Supervision of data in a wireless network

ABSTRACT

Examples of methods, systems, and computer program products relating to supervising data in a wireless network are disclosed. At least part of a system may be located between a packet data network and a base station, and/or may be at least logically separate from the base station. The system may be capable of evaluating the service provided by the base station, and may be capable of determining whether or not any action should consequently be performed. Examples of an action may include an action which may not necessarily affect en-route data packets such as outputting a report, and/or an action which may affect en-route data packets such as delaying packets, not delaying packets, and/or stopping the delaying of packets. An action which affects data packets may or may not affect data packets uniformly. An action may or may not result in an improvement in quality of user experience.

TECHNICAL FIELD

The disclosure relates to wireless networks.

BACKGROUND

A wireless network may be used to provide wireless data services to auser (also referred to as a subscriber). Data may be transferred betweena packet data network (PDN) and a user equipment (UE) associated with auser via a base station. Each base station may service one or moregroups served by one or more wireless transmitters. At any point intime, each group may include zero or any number of UEs. For example, ata particular point in time a certain base station may service 1 group, 3groups or 6 groups, with each group including zero or any number of UEs(e.g. tens of UEs).

Examples of a wireless network may include a mobile network, a Wi-Finetwork, and/or any other type of wireless network. In a mobile networkwith a core network of Universal Mobile Telecommunications System (UMTS)architecture, a base station may additionally or alternatively bereferred to as a NodeB. In a mobile network with a core network of LongTerm Evolution architecture (LTE) a base station may additionally oralternatively be referred to as an eNodeB. In a mobile network with acore network of Global System for Mobile Communications (GSM), CodeDivision Multiple Access (CDMA), or Code Division Multiple Access 2000(CDMA 2000), a base station may additionally or alternatively bereferred to as a base transceiver station or radio base station. In aWi-Fi network, a base station may additionally or alternatively bereferred to as an access point or wireless access point.

SUMMARY

In accordance with the presently disclosed subject matter, there isprovided a method of supervising data in a wireless network, comprising:noting times associated with data packets en route between a packet datanetwork and a base station; at least partly based on one or more of thenoted times, evaluating the service provided by the base station; atleast partly based on a result of the evaluating, determining whether ornot at least one action should be performed; and if determined that anyaction should be performed, performing at least one action.

In some examples of the method, the evaluating includes: estimating atleast one parameter at least partly based on one or more of the notedtimes.

In some cases of these examples, at least one of the at least oneparameter is indicative of base station queuing time.

In some cases of these examples, at least one of the at least oneparameter is a round trip time or adjusted round trip time.

In some cases of these examples, at least one of the at least oneparameter is a base station outgoing rate.

In some examples of the method, at least one of the at least one actionis performed in order to reduce the fullness of at least one queue inthe base station.

In accordance with the presently disclosed subject matter, there isprovided a system for supervising data in a wireless network,comprising: a noter configured to note times associated with datapackets en route between a packet data network and a base station; anevaluator configured, at least partly based on one or more of the notedtimes, to evaluate the service provided by the base station, andconfigured, at least partly based on a result of the evaluating, todetermine whether or not at least one action should be performed; and anaction performer delayer configured, if determined that any actionshould be performed, to perform at least one action.

In some examples, the system further comprises: a data structure inwhich the noter is configured to store times associated with datapackets.

In some examples, the system further comprises: a recognizer configuredto recognize characteristics of data packets.

In some examples, the system further comprises: a handler configured tointercept and forward data packets.

In some examples of the system, at least part of the system is locatedin the wireless network between a packet data network and one or morebase stations.

In some examples of the system, at least one of the at least one actionis performed in order to reduce the fullness of at least one queue inthe base station.

In accordance with the presently disclosed subject matter, there isprovided a computer program product comprising a computer useable mediumhaving computer readable code embodied therein for supervising data in awireless network, the computer program product comprising: computerreadable program code for causing a computer to note times associatedwith data packets en route between a packet data network and a basestation; computer readable program code for causing a computer, at leastpartly based on one or more of the noted times, to evaluate the serviceprovided by the base station; computer readable program code for causinga computer, at least partly based on a result of the evaluating, todetermine whether or not at least one action should be performed; andcomputer readable program code for causing a computer, if determinedthat any action should be performed, to perform at least one action.

In some examples of the computer program product, at least one of the atleast one action is performed in order to reduce the fullness of atleast one queue in the base station.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to understand the subject matter and to see how it may becarried out in practice, some examples will be described, with referenceto the accompanying drawings, in which:

FIG. 1 is a block diagram of an example of a wireless network, inaccordance with the presently disclosed subject matter;

FIG. 2 is a block diagram of an example of a supervisor system, inaccordance with the presently disclosed subject matter;

FIG. 3 is a flowchart of an example of a supervision method, inaccordance with the presently disclosed subject matter;

FIG. 4 is a block diagram of an example of an observer system, inaccordance with the presently disclosed subject matter;

FIG. 5 is a flowchart of an example of an observation method, inaccordance with the presently disclosed subject matter;

FIG. 6 is a block diagram of an example of an affector system, inaccordance with the presently disclosed subject matter;

FIG. 7 is a flowchart of an example of an affecting method, inaccordance with the presently disclosed subject matter;

FIG. 8 is a block diagram of an example of a mobile network with a corenetwork of UMTS/GSM architecture, in accordance with the presentlydisclosed subject matter; and

FIG. 9 is a block diagram of an example of a mobile network with a corenetwork of LIE architecture, in accordance with the presently disclosedsubject matter.

It will be appreciated that for simplicity and clarity of illustration,elements shown in the figures have not necessarily been drawn to scale.For example, the dimensions of some of the elements may be exaggeratedrelative to other elements for clarity. Further, where consideredappropriate, reference numerals may be repeated among the figures toindicate identical or analogous elements.

DETAILED DESCRIPTION OF THE DRAWINGS

Examples of methods, systems, and computer program products relating tosupervising data in a wireless network are disclosed. At least part of asystem may be located between a packet data network and a base station,and/or may be at least logically separate from the base station. Thesystem may be capable of evaluating the service provided by the basestation, and may be capable of determining whether or not any actionshould consequently be performed. Examples of an action may include anaction which may not necessarily affect en-route data packets such asoutputting a report, and/or an action which may affect en-route datapackets such as delaying packets, not delaying packets, and/or stoppingthe delaying of packets. An action which affects data packets may or maynot affect data packets uniformly. An action may or may not result in animprovement in quality of user experience.

In the description herein, numerous specific details are set forth inorder to provide a thorough understanding of the subject matter.However, it will be understood by those skilled in the art that someexamples of the subject matter may be practiced without these specificdetails. In other instances, well-known features, structures,characteristics, stages, methods, modules, elements, entities or systemshave not been described in detail so as not to obscure the subjectmatter,

Usage of the term “typically although not necessarily”, “although notnecessarily so” “such as”, “e.g.”, “possibly”, “it is possible”, “it maybe possible”, “optionally”, “say”, “for example,” “for instance”, “anexample” “one example”, “illustrated example”, “some examples”, “anotherexample”, “other examples, “various examples”, “examples”, “instances”,“one instance”, “some instances”, “another instance”, “other instances”,“one case”, “some cases”, “another case”, “other cases”, “cases”, orvariants thereof means that a particular described feature, structure,characteristic, stage, method, module, element, entity, or system isincluded in at least one example of the subject matter, but notnecessarily in all examples. The appearance of the same term does notnecessarily refer to the same example(s).

The term “illustrated example”, is used to direct the attention of thereader to one or more of the figures, but should not be construed asnecessarily favoring any example over any other.

Usage of conditional language, such as “may”, “can”, “could”, orvariants thereof should be construed as conveying that one or moreexamples of the subject matter may include, while one or more otherexamples of the subject matter may not necessarily include, certainfeatures, structures, stages, methods, modules, elements, entities orsystems. Thus such conditional language is not generally intended toimply that a particular described feature, structure, stage, method,module, element, entity or system is necessarily included in allexamples of the subject matter.

The term “non-transitory” is used to exclude transitory, propagatingsignals, but to otherwise include any volatile or non-volatile computermemory technology suitable to the application.

It should be appreciated that certain features, structures,characteristics, stages, methods, modules, elements, entities or systemsdisclosed herein, which are, for clarity, described in the context ofseparate examples, may also be provided in combination in a singleexample. Conversely, various features, structures, characteristics,stages, methods, modules, elements, entities or systems disclosedherein, which are, for brevity, described in the context of a singleexample, may also be provided separately or in any suitablesub-combination.

Usage of terms such as “observing”, “estimating”, “comparing”,“determining”, “outputting”, “reporting”, “evaluating”, “noting”,“performing”, “recognizing”, “handling”, “dropping”, “updating”,“adjusting”, “delaying”, “stopping”, “checking”, “waiting”, “causing”,“removing”, “placing”, “storing”, “intercepting”, “forwarding”,“executing”, implementing”, or the like, may refer to the action(s)and/or process(es) of a system such as any of the system(s) describedbelow, or a part thereof.

Referring now to the figures in more detail, FIG. 1 is a block diagramof an example of a wireless network 100, in accordance with thepresently disclosed subject matter.

In the illustrated example, wireless network 100 may include one or morepacket data network(s) (PDN) 190, one or more base station(s) 120, oneor more supervisor system(s) 170 and one or more user equipment(s) (UE)130. The dashed lines between elements 190, 170, 130 and 110, signifythat there may be intervening element(s) between elements illustrated inFIG. 1, but for simplicity's sake, such intervening element(s) may notbe described with reference to FIG. 1. Each base station 130 may serviceone or more groups served by one or more wireless transmitters andtherefore may service at any point in time zero or more UE(s) 110. Thesubject matter does not limit the location of any supervisor 170, butoptionally at least part of each supervisor 170 may be located in alocation between one or more PDN(s) 190 and one or more base station(s)130, and/or optionally at least part of each supervisor 170 may be inthe same location as one or more base station(s) 130 but at leastlogically separate from base station(s) 130. Such a location maypossibly enable supervisor 170 to supervise data packets on route in oneor either direction between any of PDN(s) 190 and any of base station(s)130.

For simplicity of illustration and description, a single element isillustrated in FIG. 1 and described herein for each of PDN 190,supervisor 170, and base station 130, but in some examples network 100may include a plurality of elements of one or more of these types.

Wireless network 100 may be any type of wireless network, such as amobile network, a network, another type of wireless network, acombination of any of the above, etc. If at least part of wirelessnetwork 100 is a mobile network, the mobile network may include a corenetwork of any architecture such as UMTS, GSM, LTE, CDMA, CDMA2000, anynetwork of any appropriate generation, etc.

PDN 190 may be any type of packet data network. For instance, PDN 190may be the internet, and/or any other public and/or private packet datanetwork.

Supervisor system 170 may be made up of any combination of software,hardware and/or firmware that performs the function(s) as described andexplained herein, including for instance supervision of data in mobilenetwork 100. For example, supervisor system 170 or any part thereof mayinclude a computer. The term computer in the single form herein shouldbe construed to cover a single computer and/or a plurality of computersand the term computer should be broadly construed to cover anycombination of hardware, software and/or firmware, the combinationincluding at least some hardware and having capabilities which includedata processing capabilities. For example, a computer may be speciallyconstructed for the desired purposes, and/or a computer may beselectively activated and/or reconfigured by specially constructedprogram code.

Depending on the instance, supervisor 170 may be centralized in onelocation (e.g. including one or more units at that location), orsupervisor 170 may be dispersed over more than one location in mobilenetwork 100. Therefore even in cases where at least part of supervisor170 may be located between base station 130 and PDN 190 and/or in thesame location as base station 130 but logically separate, it is possiblethat another part of supervisor 170 may be located elsewhere.

User equipment 110 may be any type of user equipment configured toaccess PDN 190 via base station 130. An example of user equipment 110may include a Smartphone, feature phone, a tablet, a PC (“personalcomputer”) connecting via a USB dongle, etc.

Base station 130 may be any type of base station associated with anyarchitecture (e.g., NodeB in UMTS, eNodeB in LTE; base transceiverstation/radio base station in GSM, CDMA, or CDMA2000; accesspoint/wireless access point in Wi-Fi, etc). For instance, base station130 may include one or more transmitters/receiver(s), one or moreantenna(s) and/or one or more other element(s).

Typically although not necessarily, data packets arriving at basestation 130 from PDN 190 may be placed in one or more queue(s) in basestation 130. Typically although not necessarily, base station 130 may beconfigured to schedule the provision of data packets, destined for UEs110 which “compete” for service, among these UEs 110. The scheduling ofdata packets may typically although not necessarily be in accordancewith a proprietary scheduling algorithm. For instance, one schedulingalgorithm may aim to maximize throughput per base station 130 (or ifbase station 130 services more than one group served by more than onewireless transmitter, then additionally or alternatively per group).Throughput may be affected by the amount of overhead and/orretransmitted packets, where the amount of overhead and/or retransmittedpackets may be dependent for instance on any of reception conditions,interference, the scheduling algorithm etc. Possibly a schedulingalgorithm which favors UE(s) 110 with the best reception conditionsrather than ignoring reception conditions when scheduling data packetsmay result in a higher throughput. Additionally or alternatively,another scheduling algorithm may be proportionally fair by aiming tomaximize throughput but allowing all competing UEs 110 at least aminimal level of service. The subject matter is not bound by anyparticular scheduling algorithm.

FIG. 2 is a block diagram of an example of a supervisor system 170, inaccordance with the presently disclosed subject matter.

Depending on the example, supervisor 170 may be configured to supervisedata in a manner which may vary between very passive to very active.

In the illustrated example, supervisor 170 may include a notes module274, an evaluator module 276, an action performer module 278, andoptionally a recognizer module 272, a handler module 280, a queue(s)module 284, and/or a data structure module 282. Any module in supervisor170 may be made up of any combination of software, hardware and/orfirmware suitable for the function(s) attributed to the module herein.

When included, recognizer 272 may, for instance, be configured torecognize one or more characteristic(s) of a data packet. The subjectmatter does not limit how recognizer 272 may recognize characteristic(s)of a data packet. For the purpose of illustration only, however, someexamples are now presented. For example, one or more characteristic(s)may be recognized using deep packet inspection. Additionally oralternatively, for example, one or more characteristic(s) may berecognized from the header(s) of the data packet. Additionally oralternatively, for example, one or more characteristic(s) may berecognized at least partly based on previous signaling in wirelessnetwork 100.

Noter 274 may, for instance, be configured to note a time associatedwith a data packet en route from PUN 190 to base station 130.Additionally or alternatively, noter 274 may for instance, be configuredto note a time associated with a data packet en route from base station130 to PUN 190. For instance, in some cases, noter 274 may note a firsttime associated with a particular (non-acknowledgement) data packet enroute from PUN 190 to base station 130, and if a reliable protocol suchas Transmission Control Protocol (TCP) is being used, note a second timeassociated with an acknowledgement data packet en route from basestation 130 to PDN 190 which acknowledges the particular data packet, ina manner which imparts that there is a relationship between the firsttime with the second time. Additionally or alternatively, noter 274 mayfor instance, be configured to note one or more characteristic(s)recognized by recognizer 272 (when included), if any.

Noter 274 may, for instance, be configured to note times and/orcharacteristics in a data structure. The data structure may be locatedin supervisor 170, e.g. data structure 282 when included, or may belocated externally to supervisor 170 but in a location accessible toe.g. noter 274 and/or evaluator 276. Additionally or alternatively,noter 274 may, for instance, note times and/or characteristics toevaluator 276 for use by evaluator 276 without necessarily storing timesand/or characteristics in a data structure.

Evaluator 276 may, for instance, be configured to evaluate the serviceprovided by base station 130, for instance at least partly based on oneor more noted times. Evaluator 276 may, for instance, be configured atleast partly on a result of the evaluating to determine whether or notone or more action(s) should be performed. The subject matter does notlimit the way in which evaluator 276 may evaluate the service and/ordetermine whether or not one or more action(s) should be performed. Thesubject matter does not limit the action(s) regarding which evaluationmay be made.

When included, handler 280 may for instance, be configured to handledata packets. For instance, when handler 280 is included, a data packeten route from PDN 190 to base station 130 and/or a data packet en routefrom base station 130 to PDN 190, may be intercepted by handler 280 andsubsequently forwarded by handler 280 in order that the data packet maycontinue to base station 130 or PDN 190.

When included, queue(s) 284 may, for instance, include one or more (datapacket) queue(s) where data packet(s) may be queued. The subject matterdoes not limit the number and/or type of queue(s) 284.

In some instances when included, data structure 282 and/or queue(s) 284may be comprised in memory, where memory or medium may refer to anymodule for storing data for the short and/or long term, locally and/orremotely.

Action performer 278 may, for instance, be configured to perform one ormore actions, at least partly based on a determination by evaluator 276.The subject matter does not limit the type(s) of action(s) which may beperformed by action performer 278.

Alternatively to the example shown in FIG. 2, system 170 may in someexamples include fewer, more and/or different modules than shown in FIG.2. Alternatively to the example shown in FIG. 2 the functionality ofsystem 170 may in some examples be divided differently among the modulesillustrated in FIG. 2. Therefore any function attributed to a certainmodule in an example herein may additionally or alternatively heperformed by different module(s). Alternatively to the example shown inFIG. 2, the functionality of system 170 described herein may in someexamples be divided into fewer, more and/or different modules than shownin FIG. 2. Alternatively to the example shown in FIG. 2, system 170 mayin some examples include additional, less, and/or differentfunctionality than described herein. For example, system 170 may includefunctionality unrelated to supervision in wireless network 100.

FIG. 3 is a flowchart of an example of a supervision method 300 inaccordance with the presently disclosed subject matter. Method 300 mayhe performed for example by supervisor 170. Supervision method 300 maybe used for instance, for supervising data in wireless system 100 in amanner which may vary between very passive to very active.

As the timing and/or circumstance(s) for performing various stage(s) inmethod 300 may vary depending on the example of supervision, forsimplicity of description the timing and/or circumstance(s) are ignoredin the description of method 300.

In the illustrated example, in optional stage 305, one or more factorsrelating to method 300 may be determined by supervisor 170, for instanceby evaluator 276. Factor(s) may he determined, for instance, by way ofreceived input, e.g. from an operator (via an input device such as akeypad, keyboard, mouse and/or any other input device) and/or e.g. froman external element (external to supervisor 170) such as a planningtool, database and/or any other element. Additionally or alternatively,factor(s) may he determined, for instance, based on experience and/orapplicable condition(s) (e.g. any of current time of day, location ofbase station 130, etc) The subject matter does not limit the factor(s)which may optionally he determined in stage 305. In some other examples,stage 305 may be omitted if no factors are to he determined.

Depending on the example, a data packet en route from PDN 190 to basestation 130 or en route from base station 130 to PDN 190 may or may notbe handled by supervisor 170, e.g. by handler 280. If handled, then inoptional stage 315, handler 280 may handle the data packet, e.g.intercept the data packet which may subsequently be forwarded.

In the illustrated example, in optional stage 320, characteristic(s) thedata packet may be recognized by supervisor 170, for instance byrecognizer 272. For instance, characteristic(s) may be recognized usingdeep packet inspection, from packet header(s), and/or at least partlybased on earlier signaling, etc. In some other examples, stage 320 maybe omitted, for instance if characteristic(s) are not relevant for laterstages of method 300.

In the illustrated example, in stage 325, supervisor 170, for instancenoter 274, may note one or more time(s) associated with the data packetand/or may note recognized characteristic(s). For instance, for a packeten route from PDN 190 to base station 130 a time associated with travelin that direction and possibly if there is a correspondingacknowledgement packet, a time associated with travel of thecorresponding acknowledgement packet in the opposite direction may benoted.

Depending on the instance, stages 315 to 325, when performed, may beperformed fir different data packets in parallel, or the stages may becompleted for one data packet before being performed for another datapacket.

In the illustrated example in optional stage 330, an adjustment variablemay be updated by supervisor 170, e.g. by evaluator 276. For instance,an adjustment variable may attempt to adjust for cause(s), not directlyrelated to base station 130, which may affect the value of a serviceparameter. The subject matter does not limit how the adjustment variablemay be updated. Although updating may occur at any time, for simplicityof illustration, stage 330 is illustrated after stage 325. In some otherexamples, stage 330 may be omitted, for instance if cause(s) notdirectly related to base station 130 may be ignored, or if an adjustmentvariable may not easily and/or reliably be determined. In some of theseother examples where stage 330 may be omitted, the adjustment variablemay be a constant configurable value.

In the illustrated example, in optional stage 337, a service parametermay be estimated by supervisor 170 (e.g. by evaluator 276) for anindividual user equipment 110 (e.g. any one of a plurality of userequipments 110; any one of a plurality of user equipments 110 associatedwith any of one or more groups served by one or more wirelesstransmitters; any one of a plurality of user equipments 110 whichcompete for service in base station 130 as scheduled by a scheduler;etc). Additionally or alternatively, a service parameter may beestimated by supervisor 170 (e.g. by evaluator 276) for a plurality ofuser equipments 110 (e.g. a plurality of user equipments 110; aplurality of user equipments 110 associated with any of one or moregroups served by one or more wireless transmitters; a plurality of userequipments 110 which compete for service in base station 130 asscheduled by a scheduler; etc). The subject matter does not limit theestimated service parameter, but for the sake of further illustration tothe reader, some instances are now provided.

For instance, a possible service parameter 110 for an individual userequipment 110 may reflect and/or be indicative of one or more round triptime(s), one or more adjusted round trip time(s) (e.g. difference(s) ofround trip time and round trip adjustment), one or more base stationqueuing time(s), one or more base station outgoing rate(s), and/or oneor more quotient(s)for a round trip time or adjusted round trip timedivided by the difference between an outgoing rate and an incoming rateto base station 130, etc. Optionally, a function (e.g. average, sum,etc) may be used in estimating a possible service parameter 110. A roundtrip time may for instance be estimated as the difference between a timenoted for a data packet en route toward the individual UE 110 and thetime noted for the corresponding acknowledgement packet. A round triptime adjustment may for instance be an adjustment variable for a roundtrip time which may attempt to adjust for cause(s) not directly relatedto any queuing time in base station 130 which may affect the round triptime. The adjustment variable may or may not be constant and/orconfigurable. A base station outgoing rate to an individual UE 110 mayfor instance be estimated as a difference between two times noted fortwo different acknowledgement packets (not necessarily sequential)divided by the difference between the noted sequence numbers.

Additionally or alternatively, for instance, a possible serviceparameter for a plurality of user equipments 110 may reflect and/or beindicative of service parameters for individual user equipments 110included in the plurality, e.g. by way of a function such as average,sum, etc. Continuing with this instance, a possible service parametermay include an average of round trip times or functions thereof (e.g.round trip time minus round trip time adjustment) for various userequipments 110 included in the plurality, an average of base stationqueuing times for various user equipments 110 included in the plurality,a sum of base station outgoing rate from base station 130 for varioususer equipments 110 included in the plurality 110, and/or an average ofquotients for various user equipments 110, etc. Additionally oralternatively, for instance, a possible service parameter for aplurality of user equipments 110 may not necessarily reflect and/or beindicative of service parameters for individual user equipments 110included in the plurality but may be estimated otherwise such as a basestation outgoing rate from base station 130 to the plurality of UEs 110and/or a parameter indicative of service provision by base station 130to only one (or to more than one) of the plurality of UEs 110, etc.

In the illustrated example, in optional stage 349, an estimated serviceparameter may be compared to a threshold by supervisor 170 e.g. byevaluator 276.

In instance(s) where stage 330, 337 and/or 349 may be performed, thestage(s) may be performed one time or a plurality of time(s). Ifperformed a plurality of times, the adjustment variables, estimatedparameters, and/or thresholds from different iterations may relate tothe same user equipment(s) 110 (and/or the same plurality of userequipments 110) and/or to different user equipments) 110 (and/or todifferent pluralities of user equipments 110).

One or more iteration(s) of stage 337 and/or 349 may for instance beperformed as part of an evaluation of the service provided by basestation 130. An evaluation of service may, for instance, additionally oralternatively he at least partly based on one or more noted times. Thesubject matter does not limit how service is evaluated, and theevaluation may additionally or alternatively include stage(s) unrelatedto estimating parameter(s) and/or comparing threshold(s).

In the illustrated example, in stage 365, at least partly based on aresult of the service evaluation, supervisor 170, for instance evaluator276, may determine whether or not to perform one or more action(s).

In the illustrated example, if it is determined to perform at least oneaction (yes to stage 370), then in the illustrated example, in stage 375at least one action may be performed, for instance by action performer278. The subject matter does not limit which action(s) may be performed.For instance, examples of an action may include an action which may notnecessarily affect data packet(s) traveling wireless network 100, and/oran action which may affect data packet(s) traveling in wireless network100. For the sake of further illustration an example of possibleaction(s) will now be described. In this example, at least one actionmay be performed in order to reduce the fullness of at least one queuein base station 130. In some cases of this example, the evaluation ofservice provided by base station 130 may include an evaluation of thefullness of at least one queue in base station 130. In some of thesecases, the evaluation of the fullness may include estimation of aservice parameter which may be negatively impacted by base stationqueuing time(s) and therefore may be indicative of the status (e.g.fullness) of base station queue(s). The subject matter does not limitwhich action(s) may be performed to reduce the fullness of queue(s), andany suitable action may be performed such as delaying packet(s), etc.See also the description with reference to FIGS. 4 to 7 regardingpossible examples of actions that may be performed, which may or may notbe the same as action(s) performed to reduce the fullness of queue(s).

If it is not determined to perform an action (no stage 370), thendepending on the example one or more action(s) may or may not beperformed in stage 385.

In some instances, stages 365 to 385 may not necessarily be performedfor each data packet, but may be performed for instance, after eachpredefined number of data packets.

In the illustrated example after stage 375 or 385, method 300 may end.Method 300 or a part thereof may or may not be repeated, for instance byiterating to any appropriate stage in method 300. If repeated the timingand/or circumstance(s) for repetition may vary depending on the exampleof supervision. Possibly, even if method 300 is not repeated, or betweenrepetitions, one or more stage(s) of method 300 may be performed, forother purpose(s) and/or to maintain routine for supervisor 170.

In some instances, stages 315 to 325 may have continued to be performedas data packets may have been handled while stages 330 to 375 were beingperformed, but in other examples stages 315 to 325 may not havecontinued to be performed while stages 330 to 375 were being performed.

Alternatively to the example illustrated in FIG. 3, stages which areshown in as being executed sequentially may in some other examples beexecuted in parallel, and/or stages shown as being executed in parallelmay in some other examples be executed sequentially. Alternatively toany of the example illustrated in FIG. 3, method 300 may in some otherexamples include more, fewer and/or different stages than illustrated.For instance, method 300 may, for instance, additionally oralternatively include any of the stage(s) described with reference toFIG. 5 or FIG. 7. Alternatively to the example illustrated in FIG. 3,stages may in some other examples be executed in a different order thanillustrated.

FIG. 4 is a block diagram of an example of an observer system 470, inaccordance with the presently disclosed subject matter. Observer system470 may be configured to observe congestion in wireless system 100and/or any observable situation in wireless network 100. Observer system470 may be an example of supervisor system 170, and therefore thedescription of system 470 may not necessarily repeat details describedwith reference to system 170.

In the illustrated example, observer system 470 may include a recognizermodule 472, a noter module 474, a congestion evaluator module 476, areporter module 478, and optionally a handier module 480 and/or datastructure module 482. Modules 472, 474, 476, 478, 480 and/or 482 may beexamples of modules 272, 274, 276, 278, 280 and/or 282 respectively. Anymodule in observer 470 may he made up of any combination of software,hardware and/or firmware suitable for the function(s) attributed to themodule herein. For example, observer system 470 or any part thereof mayinclude a computer.

Handler module 480 may be optional since depending on the instance,recognizer 472 and/or noter 474 may be configured to perform function(s)relating to a data packet en route from PDN 190 and base station 130without handler 480 handling the data packet, or may be configured toperform function(s) relating to a data packet en route from PDN 190 andbase station 130 in the case that handler 480 handles the data packet.Additionally or alternatively, depending on the instance, recognizer 472and/or noter 474 may be configured to perform function(s) relating to adata packet en route from base station 130 to PDN 190 without handler480 handling the data packet, or may be configured to performfunction(s) relating a data packet en route from base station 130 to PDN190 in the case that handler 480 handles the data packet. For instance,a data packet on the way from PDN 190 to base station 130 or vice versa,may or may not be intercepted by handler 480 and may or may not besubsequently forwarded by handler 480 in order that the data packet maycontinue to base station 130 or PDN 190.

For instance recognizer 472 may be configured to recognize one or morecharacteristic(s) of a data packet. The subject matter does not limithow recognizer 472 may recognize characteristic(s) of a data packet. Forthe purpose of illustration only, however, some examples are nowpresented.

For example, one or more characteristic(s) may be recognized by usingdeep packet inspection.

Additionally or alternatively, for example, one or morecharacteristic(s) may be recognized from the header(s) of the datapacket. For instance, depending on the example any of sequence number,type of data packet, tunnel identifier, destination address, sourceaddress, destination port, source port etc may be recognized fromheader(s) of the data packet. Additionally or alternatively, forinstance, the layer 7 header may indicate the type of user traffic suchas browsing, streaming video, streaming audio, downloading, etc.Additionally or alternatively, for instance, for a data packet which isan acknowledgement data packet such as in a reliable protocol, e.g. TCP,a possible characteristic may be the acknowledgement number whichenables correspondence to corresponding data packet(s) for which theacknowledgement data packet is acknowledging receipt.

Additionally or alternatively, for example, one or morecharacteristic(s) may be recognized at least partly based on previoussignaling in wireless network 100. For instance, a group (served by awireless transmitter) and/or base station identifier and/or UEidentifier may have been determined from previous signaling. Thesignaling may have included, for instance, a Service Area Identifier (orthe equivalent) which may be used to identify a service area comprisingone or more groups served by one or more wireless transmitters in thesame location area and may therefore be considered to be an example of agroup (served by a wireless transmitter) and/or base station identifier.The signaling may have additionally or alternatively included, forinstance, a permanent Non-Access Stratum UE identity (or equivalent)which may be considered to be an example of a UE identifier. A group(served by a wireless transmitter) and/or base station identifier and/ora UE identifier may have been stored in an accessible location torecognizer 472, perhaps in association with an associated identifier(e.g. tunnel identifier, destination address, source address,destination port and/or source port etc) which may be included in a datapacket header, so that recognizer 472 may be configured to recognizethat the data packet relates to a certain group served by a wirelesstransmitter, base station, and/or UE 110 at least partly based on thestored identifier(s). For instance, recognizer 472 may thereby becapable of recognizing the particular UE 110 for which the data packetis destined or from which the data packet originated. Additionally oralternatively, for instance, recognizer 472 may thereby be capable ofrecognizing the particular group served by a wireless transmitter and/orbase station 130 associated with the particular UE 110 for which thedata packet is destined or from which the data packet originated.

Noter 474 may, for instance, be configured to note a time associatedwith a data packet en route from PDN 190 to base station 130, e.g. anyof the time that the packet passes the location of noter 474 (e.g.without handling), the time the data packet is intercepted by handler480, the time the data packet is forwarded by handler 480, etc.Additionally or alternatively, rioter 474 may for instance, beconfigured to note a time associated with a data packet en route frombase station 130 to PDN 190, e.g. any of the time that the packet passesthe location of noter 474 (e.g. without handling), the time the datapacket is intercepted by handler 480, the time the data packet isforwarded by handler 480, etc. The data packet traveling in eitherdirection may or may not be an acknowledgement data packet. For instanceif a reliable protocol such as TCP is being used, an acknowledgementdata packet may be sent to acknowledge receipt for any bytes prior to acertain sequence number. In some cases, noter 474 may note a first timeassociated with a particular (non-acknowledgement) data packet travelingfrom PDN 190 to base station 130 and note a second time associated withan acknowledgement data packet traveling from base station 130 to PDN190 which acknowledges the particular data packet, in a manner whichimparts that there is a relationship between the first time and thesecond time (and/or imparts that there is a relationship between bothtimes and the particular (non-acknowledgement) data packet).

Additionally or alternatively, noter 474 may, for instance, beconfigured to note one or more characteristic(s) recognized byrecognizer 472. For instance, noter 474 may in some cases reference oneor more noted time(s) to any of a sequence number, UE identifier, group(served by a wireless transmitter) and/or base station identifier, datapacket type, etc.

Noter 474 may, for instance, be configured to note times and/orcharacteristics in a data structure. The data structure may be locatedin observer 470, e.g. data structure 482 when included, or may belocated externally to observer 470 but in a location accessible to e.g.noter 474 and/or congestion evaluator 476. Additionally oralternatively, noter 474 may note the times and/or characteristics tocongestion evaluator 476 for use by evaluator 476 without necessarilystoring times and/or characteristics in a data structure.

Congestion evaluator 476 may, for instance, be configured to evaluatewhether or not a set comprising one or more groups served by one or morewireless transmitters is congested. Depending on the example, a set mayinclude all of the group(s) serviced by base station 130 or may includefewer group(s) than all the group(s) serviced by base station 130. Thesubject matter does not limit the way in which congestion evaluator 476may evaluate congestion. Some examples of stages which congestionevaluator 476 may perform to evaluate whether or not a set is congestedare described below with reference to FIG. 5.

Additionally or alternatively, congestion evaluator 476 may, forinstance, be configured to evaluate one or more parameter(s) relating tobase station service, and/or evaluate with respect to observablesituation(s) in wireless network 100 without necessarily evaluatingwhether or not a set is congested.

Reporter 478 may, for instance, be configured to output a report ofcongestion, if congestion evaluator 476 determined that a set iscongested. Optionally, reporter 478 may, for instance, be configured tooutput a report of non-congestion, if congestion evaluator 476determined that a set is not congested. Additionally or alternatively,reporter 478 may, for instance, be configured to output a reportregarding base station service, not necessarily relating to congestion.The subject matter does not limit the content and format of any reportoutputted by reporter 478 and/or the destination of the output. Forinstance, if determined that there is congestion a report may include anindication of congestion, and/or may indicate a level of congestion. Forinstance, the report may be outputted to an operator (e.g. via adisplay, printer and/or any other output device), and/or to an elementexternal to observer 470 (e.g. a planning tool, database, and/or anyother element).

Alternatively to the example shown in FIG. 4, system 470 may in someexamples include fewer, more and/or different modules than shown in FIG.4. Alternatively to the example shown in FIG. 4 the functionality ofsystem 470 may in some examples be divided differently among the modulesillustrated in FIG. 4. Therefore any function attributed to a certainmodule in an example herein may additionally or alternatively beperformed by different module(s). Alternatively to the example shown inFIG. 4, the functionality of system 470 described herein may in someexamples be divided into fewer, more and/or different modules than shownin FIG. 4. Alternatively to the example shown in FIG. 4, system 470 mayin some examples include additional, less, and/or differentfunctionality than described herein. For example, system 470 may includefunctionality unrelated to observation in wireless network 100.

FIG. 5 is a flowchart of an example of an observation method 500 inaccordance with the presently disclosed subject matter. Method 500 maybe performed for example by observer 470. Observation method 500 may beused for instance, for observing congestion in wireless system 100and/or observing any situation in wireless network 100. Observationmethod 500 may be an example of supervision method 300, and thereforethe description of method 500 may not necessarily repeat detailsdescribed with reference to method 300.

In the illustrated example, in optional stage 505, one or more factorsrelating to method 500 may be determined, by observer 470, for instanceby congestion evaluator 476. Factor(s) may be determined by way ofreceived input, e.g. from an operator (via an input device such as akeypad, keyboard, mouse and/or any other input device) and/or from anexternal element (external to observer 470) such as a planning tool,database and/or any other element. Additionally or alternatively,factor(s) may be determined based on experience and/or applicablecondition(s) (e.g. any of current time of day, location of set for whichcongestion is being evaluated, etc). Stage 505 may be an example ofstage 305.

The subject matter does not limit the factor(s) which may be determinedin stage 505, but for the sake of further illustration to the reader,some instances will now be presented. For instance, factor(s) mayinclude any of the following: how frequently congestion is evaluated,threshold(s), a time span during which a particular user equipment 110would need to be associated with a set (at any time during the timespan) in order for the particular user equipment 110 to be consideredduring the congestion evaluation, service parameter(s) associated withany user equipment 110, initial adjustment variable(s) (if not constantbut configurable), how to update an adjustment variable (if notconstant), constant adjustment variable (if constant and configurable),minimum value for adjustment variable (if not constant butconfigurable), a time duration (e.g. which may or may not be equivalentto the time span) for which congestion is evaluated, function(s) of userequipment service parameters, the number of time(s) during a timeduration that a comparison is made to a threshold, how to determinewhether or not a set is congested based at least partly on thecomparison result, a percentage of user equipments for evaluatingcongestion, when to report, and/or what to report, etc. In some otherexamples, stage 505 may be omitted if no factors are to be determined.

Optionally, method 500 or a part thereof (e.g. from stage 510 until theend) may be repeated at any frequency. For instance the frequency maydepend on a determination made in stage 505.

In the illustrated example, in stage 507, a time duration may begin. Atime duration may be a duration for which congestion is evaluated aswill be explained in more detail with reference to stage 560.

In the illustrated example, in stage 510, a time span may begin. Whenpossible, a service parameter may be estimated for each of a pluralityof user equipments 110 associated with a set (at any time) during thattime span as will be described below. As will be described below, it maynot necessarily be possible to estimate a performance parameter forevery user equipment 110 which may be associated with the set duringthat time span due to lack of information.

In the illustrated example, in optional stage 515, a data packettraveling in either direction (from PDN 190 to base station 130servicing the set or from base station 130 to PDN 190) may optionally behandled by observer 470, e.g. by handler 480 intercepting andsubsequently forwarding the packet (e.g. after stage 520). However, insome other examples, stage 515 may be omitted and the data packet maynot be handled. Stage 515 may be an example of stage 315.

In the illustrated example, in stage 520, characteristic(s) of the datapacket may be recognized by observer 470, for instance by recognizer472. For instance, characteristic(s) may be recognized using any of deeppacket inspection, from packet header(s), and/or at least partly basedon earlier signaling, etc. Stage 520 may be an example of stage 320.

In the illustrated example, in stage 525, observer 470, for instancenotes 474, may note one or more time(s) associated with a data packetand/or recognized characteristic(s). For instance, for a packet en routefrom PDN 190 to base station 130 the time that the time that the packetpasses the location of noter 474 (e.g. without handling), the time thedata packet is intercepted, or the time the data packet is forwarded maybe noted. Possibly, if there is a corresponding acknowledgement datapacket, a time for the corresponding acknowledgement packet such as thetime the acknowledgement packet passes the location of rioter 474 (e.g.without handling), the time the acknowledgement packet is intercepted,or the time the acknowledgement packet is forwarded may be noted, e.g.with reference to the corresponding data packet which travelled in thedirection from PDN 190 to base station 130. Stage 525 may be an exampleof stage 325.

In the illustrated example in optional stage 530, an adjustment variablemay be updated by observer 470, e.g. by congestion evaluator 476. Forinstance, assume that a service parameter for user equipment 110 forwhich the data packet is destined is at least partly dependent on thetime noted for the data packet and the time noted for the correspondingacknowledgement data packet. (if the acknowledgement data packetacknowledged more than one data packet which traveled toward destineduser equipment 110, it is assumed herein for simplicity of descriptionthat the noted time is the time associated with the last acknowledgeddata packet. However in other examples the time may be a function oftimes associated with the acknowledged data packets, mutatis mutandis).The difference between the time noted for the data packet traveling inthe direction toward user equipment 110 and the time noted for thecorresponding acknowledgement data packet may be caused by one or morecauses, and may not necessarily be solely due to base station queuingtime (e.g. time between when the data packet arrived at base station 130and when the data packet left base station 130 on the way to userequipment 110 which may reflect the service provided by base station 130to user equipment 110). Cause(s) unrelated to the base station queuingtime may include cause(s) related to the base station (but not to thebase station queuing time) and/or cause(s) unrelated to the basestation. Depending on the instance, any cause(s) unrelated to the basestation queuing time may be ignored, or an adjustment variable may beestimated in order to attempt to adjust for these other cause(s). Theadjustment variable associated with a specific parameter may beparticular to user equipment 110, may be common to all group(s) servedby wireless transmitter(s) in the set, or may be common to a subset ofgroups served by wireless transmitter(s) comprised in the set.

The subject matter does not limit how the adjustment variable may beupdated, but for the sake of further illustration to the reader, aninstance is now provided.

Consider that the adjustment variable is trying to estimate the minimumperiod between when a certain data packet traveling toward UE 110 wouldbe observed (with or without handling) by observer 470 and acorresponding acknowledgement would be observed (with or withouthandling) by observer 470 when there would be practically no queuingtime between the time of arrival of the certain data packet at basestation 130 and the time of leaving of the certain data packet from basestation 130, and therefore the length of the period would be dependenton cause(s) other than the base station queuing time. Such an adjustmentvariable is also termed herein as “round trip time adjustment”. Forinstance such an adjustment variable may be initially updated (set) to avalue such as 10 or 20 ms. The adjustment variable may be reset to sucha value, for instance any time wireless network 100 may be reconfigured(e.g. adding, changing, and/or deleting an element in wireless network100). The adjustment variable may optionally be updated by slowly beingincreased (e.g. 1 ms per hour). However, if the difference between thetime noted for a data packet traveling toward user equipment 110 and thetime noted for the corresponding acknowledgement data packet is lessthan the current adjustment variable, the adjustment variable may beupdated to equal a minimum value (e.g. initial value) so as to reflect aminimum period. If the adjustment variable is specific to a particularuser equipment 110, then the adjustment variable may be updated to theminimum value only if the difference relates to that user equipment 110,but if the adjustment variable is common to all groups (s) or to asubset of group(s) comprised in a set, then the adjustment variable maybe updated to the minimum value provided the difference relates to anyuser equipment 110 associated with any of the group(s) or with any ofthe subset of group(s).

Although the updating in stage 530 may occur at any time, as describedabove, for simplicity of illustration, stage 530 is illustrated betweenstages 525 and 535. Stage 530 may be an example of stage 330.

In some other examples, stage 530 may be omitted, for instance ifcause(s) not directly related to base station 130 may be ignored, or ifan adjustment variable may not easily and/or reliably be determined. Insome of these other examples where stage 530 may be omitted, theadjustment variable may be a constant configurable value.

In the illustrated example, in stage 535, a service parameter may beestimated for a given user equipment 110 (to which the current datapacket is destined) by observer 470, for instance by congestionevaluator 476. The service parameter may provide some sort of indicationof service that is being provided by base station 130 to that userequipment 110. Possibly, a service parameter may be negatively affectedby the queuing time in base station 130, and in this case the parametermay be considered indicative of base station queuing time. Stage 535 maybe an example of stage 337. The subject matter does not limit theestimated service parameter, but for the sake of further illustration tothe reader, some instances are now provided.

For instance, a possible service parameter may estimate a round triptime (e.g. the difference between the time noted for the current datapacket traveling to the given user equipment 110 and the time noted forthe corresponding acknowledgement data packet). Additionally oralternatively, for instance a possible service parameter may estimate afunction (e.g. average, sum, etc) of a plurality of round trip times,e.g. with each round trip time e.g. reflecting the time noted for acertain data packet traveling to the given user equipment 110 and thetime noted for the corresponding acknowledgement data packet. Forinstance, additionally or alternatively, a possible service parametermay estimate an adjusted round trip time (e.g. round trip time minus around trip time adjustment). Additionally or alternatively, for instancea possible service parameter may estimate a function (e.g. average, sum,etc) of a plurality of adjusted round trip times, with each round triptime e.g. reflecting a round trip time and round trip time adjustment.Additionally or alternatively, for instance, a possible serviceparameter may be indicative of base station queuing time. Additionallyor alternatively, for instance, a possible service parameter may be afunction (e.g. average, sum, etc.) of parameters indicative of basestation queuing times. Additionally or alternatively, for instance, apossible service parameter may estimate a base station outgoing rate(e.g. the difference between two times noted for two differentacknowledgement packets, not necessarily sequential, from the given UE110 divided by the difference between the noted sequence numbers). It isnoted that since an outgoing rate may rely on acknowledgement packetswhich are not necessarily sequential, meaning not necessarily followingone another in order; an outgoing rate may possibly be calculated evenwhen intervening packet(s) relate to a protocol which is not necessarilyreliable, e.g. User Datagram Protocol (UDP). Additionally oralternatively, for instance, a possible service parameter may estimate afunction (e.g. average, sum, etc) of a plurality of outgoing rates, witheach outgoing rate e.g. reflecting two times noted for acknowledgementpackets and sequence numbers. Additionally or alternatively, forinstance, a possible service parameter may estimate a quotient for around trip time or adjusted round trip time divided by the differencebetween an outgoing rate and an incoming rate to base station 130.Additionally or alternatively, for instance, a possible serviceparameter may estimate a function (e.g. average, sum, etc) of aplurality of quotients. If times were already noted for a plurality ofpackets destined to the given UE 110 during the time span, the estimatedparameter in this iteration of stage 535 may reflect the plurality ofpackets, a subset of the packets or even only one or two (e.g. last) ofthe packets. If the estimated parameter for the given UE 110 includes afunction (e.g. average, sum, etc), the function may be updated asnecessary, e.g. in iteration(s) of stage 535 during the time span.

It is noted that even though a service parameter may be estimated for aparticular user equipment 110, the service parameter may be affected bythe service provided to other user equipments 110, if any, associatedwith the set (and may possibly be affected by the service provided toother user equipments 110 associated with base station 130, if any, evenif not necessarily associated with the same set, when the base stationservices more than the set). For instance, assuming other userequipment(s) 110 may be associated with the set and that base station130 includes a scheduler which does not want to always starve all ofthese other user equipment(s) 110 in the set, then the service parameterfor particular user equipment 110 may possibly at least sometimesreflect a poorer service than if only the particular user equipment 110was being serviced in the set.

Depending on the instance, stages 515 to 535 may be performed fordifferent data packets in parallel, or the stages may be completed forone data packet before being performed for another data packet.

In the illustrated example, in stage 540, it is determined if the timespan has elapsed. If no then in the illustrated example method 500iterates for further data packet(s), if any.

It may be possible that for one or more UE 110 associated with the set(at any time) during the time span, a service parameter may notnecessarily be estimated. For instance a service parameter may not beestimated if there is insufficient information. There may beinsufficient information, e.g. if a data packet destined for given UE110 passed or was handled by observer 470 before the beginning of thetime span, even if the corresponding acknowledgement data packet isobserved by observer 470 during the time span, if the time theacknowledgment data packet from given UE 110 passes or is handled byobserver 470 is after the time span even if the corresponding datapacket traveling from PDN 190 to base station 130 was observed byobserver 470 during the time span, if no acknowledgement is sent (e.g.in UDP), if no data packet en route given UE 110 nor correspondingacknowledgement data packet is observed by observer 470 during the timespan, and/or if only one acknowledgement data packet is observed byobserver 470 during the time span (and two are needed to estimate theservice parameter), etc.

If the time span has elapsed, then in the illustrated example, method500 may proceed to the next stage.

In the illustrated example, in optional stage 545, for each of aplurality of UEs 110 for which a service parameter was estimated, theestimated service parameter may be compared to a threshold by observer470, e.g. by congestion evaluator 476. Stage 545 may be an example ofstage 349. The subject matter does not limit the threshold. Thethreshold may be the same for all UEs 110 in the set, may vary fordifferent UEs 110, may be constant over time, and/or may vary over time,etc. In some examples, stage 545 may be omitted, for instance if stage555 is performed instead.

In the illustrated example, in optional stage 550 observer 470, e.g.congestion evaluator 476, may estimate a service parameter for theplurality of UE's 110 (for which respective service parameters wereestimated) which is a function of the respective estimated serviceparameters. For instance, the function may be an average or a sum of theestimated parameters fur the plurality of UEs 110. Possibly, a serviceparameter may be negatively affected by the queuing time in base station130 for data packet(s) destined for any of the plurality of UEs 110, andin this case the parameter may be considered indicative of base stationqueuing time. Stage 550 may be an example of stage 337.

In the illustrated example, in optional stage 555, a service parameterwhich was estimated in stage 550 by way of a function of the estimatedparameters for the plurality of UEs 110 may be compared to a thresholdby observer 470, e.g. by congestion evaluator 476. Stage 555 may be anexample of stage 349. The subject matter does not limit the threshold.The threshold may be constant over time, and/or may vary over time, etc.In some examples, stages 550 and/or 555 may be omitted, for instance ifstage 540 was performed instead.

In the illustrated example, in stage 560 it may be determined if a timeduration for which congestion is being evaluated is over. For instance,a time duration may include an integer number of time spans so thatstage 545 and/or 555 may be repeated more than once in order todetermine if the set is congested. Therefore in the illustrated exampleif the result of the determination is that the time duration is notover, method 500 may iterate to stage 510 for another time span. Inexamples where the time duration is different than a time span but maynot include an integer number of time spans, a similar consequence ofthe time duration not being over may occur, mutatis mutandis. If only acomparison relating to one time span is necessarily made (in stage 545and/or 555) in order to determine if the set is congested then the timeduration may be the same as the time span and separate stages 507 and560 may be omitted.

If the time duration is over (yes to stage 560) then in stage 565,observer 470, e.g. congestion evaluator 476, may determine whether ornot the set is congested at least partly based on comparison result(s).Stage 565 may be an example of stage 365.

The subject matter does not limit how it may be determined whether ornot the set may be congested, but for the sake of further illustrationto the reader, some instances are now presented.

For instance, assume that during the time duration, there may be apredetermined percentage of user equipments 110 associated with a setfor which the respective estimated parameter when compared to arespective threshold is indicative of poor service to the respectiveuser equipment 110. Further assuming a parameter of round trip time oradjusted round trip time estimated for any user equipment 110, aparticular user equipment 110 may be considered to be poorly serviced,if e.g. the estimated parameter is above a threshold. In this instance,if for a predetermined percentage of user equipments 110 the comparisonis indicative of poor service to the respective HE 110, then it may bedetermined that the set is congested. If stage 545 and/or 555 isperformed more than once during the predetermined time duration, thendepending on the instance, it may be determined that the set iscongested if there is a predetermined percentage (although notnecessarily comprising each time the same user equipments 110) each timethe comparison is made, at least one time that the comparison is made,and/or most of the time(s) that a comparison is made, etc.

Additionally or alternatively, assume that during the time duration,when comparing to a threshold a service parameter, which is an averageof respective service parameters estimated for a plurality of userequipments 110 associated with a set, the result of the comparison isindicative of poor service to the set. Assuming an estimated parameterof round trip time or adjusted round trip time for any user equipment110, it may be considered that there is poor service to the set if theaverage of the estimated parameters is above the threshold. In thisinstance, it may be determined that the set is congested. If stage 545and/or 555 is performed more than once during the predetermined timeduration, then depending on the instance, it may be determined that theset is congested if the average is indicative of poor service whencompared to the threshold (although the average may not necessarily beeach time a function of service parameters for the same user equipments110) each time the comparison is made, and/or at least one time that thecomparison is made, most of the time(s) that a comparison is made, etc.

Possibly, if a report of congestion may include a level of congestion,stage 565 may also include a determination of a level of congestion. Thesubject matter does not limit how a level of congestion is determinedbut for the sake of further illustration to the reader, some instancesare now provided.

For instance, assuming that a predetermined percentage of UEs 110 havingestimated service parameters above or below threshold(s) it isindicative of congestion, the actual percentage (equal to or higher thanthe predetermined percentage) may he indicative of the level ofcongestion. Continuing with this instance, if a percentage of say 80% isindicative of congestion, then a percentage of say 90% may possibly beindicative of higher congestion than a percentage of say 85%.Additionally or alternatively, for instance, the amount that anestimated parameter for a UE 110 may be above or below a threshold maybe indicative of the congestion level. Continuing with this instance,when considering a predetermined percentage of UEs 110 with an estimatedparameter above an associated threshold as indicative of congestion, theaverage amount that an estimated parameter is above a threshold, themaximum amount that an estimated parameter is above a threshold, and/orthe minimum amount that an estimated parameter is above a threshold, etcmay be indicative of the congestion level. Continuing with thisinstance, if the maximum amount (and/or average, minimum, etc) above thethreshold is lower, then it may possibly be indicative of a lowercongestion level than if the maximum amount (and/or average, minimum,etc) is higher. Additionally or alternatively, for instance, assumingthat an average of estimated parameters being above or below a thresholdis indicative of congestion, the amount that the average is above orbelow the threshold may be indicative of the congestion level.Continuing with this instance, if the amount above the threshold islower, then it may possibly be indicative of a lower congestion levelthan if the amount were higher. Additionally or alternatively, forinstance, assuming that a comparison is made a plurality of times, and acertain number of time(s) out of the plurality that comparison result(s)is/are indicative of congestion may be considered to be indicative ofcongestion, then the actual number of time(s) equal to or greater thanthe certain number of time(s) that comparison result(s) is/areindicative of congestion may be indicative of the level of congestion.Continuing with this instance, if comparisons are performed four times,and it is considered indicative of congestion if at least one time thecomparison result is indicative of congestion, then if four times thecomparison result is indicative of congestion, it may possibly beindicative of a higher level of congestion than if only once thecomparison result is indicative of congestion.

Assuming stage 545 and/or 555 are performed a plurality of times duringa time duration, the determination in stage 565 may be based onresult(s) of comparing from one or more iteration(s) of stage 545 and/or555, and therefore may be considered to be at least partly based on aresult of comparing from at least one of the iterations.

In the illustrated example, if it is determined that the set iscongested (yes to stage 570), then in the illustrated example in stage575 a report relating to the congestion may be outputted by observer470, e.g. by reporter 478. If not (no to stage 570), then in theillustrated example in stage 580 a report may or may not be outputted.Stage 570 may be an example of stage 370. Stage 575 may be an example ofstage 375. Stage 580 may be an example of stage 385.

As mentioned above, a report may be of any format and may include anycontent. For instance if congestion is determined the report may includean indication of congestion and/or an indication of the level ofcongestion. If a report is outputted when it is not determined that theset is congested, the report may include for instance an indication thatit was not determined that the set was congested. The report may beoutputted to an operator and/or to an external element.

Additionally or alternatively, a report may be outputted which may notnecessarily be related to congestion, but may additionally oralternatively be related to one or more observable situation(s) inwireless network 100. For instance, a report may include estimatedparameter(s), and/or an indication of a relationship between estimatedparameter(s) and respective threshold(s). In some cases of thisinstance, such a report may regard the status of one or more queue(s) inbase station 130, e.g. if the estimated parameter(s) may be negativelyimpacted by base station queuing time(s) and therefore may be indicativeof the status of base station queue(s). (The status of base stationqueue(s) may be an example of an observable situation in wirelessnetwork 100.)

Outputting a report (or equivalently reporting) may be considered anexample of an action which may not necessarily affect data packet(s) enroute between PDN 190 and base station 130 (e.g. traveling from PDN 190to base station 130 and/or from base station 130 to PDN 190).

In the illustrated example, method 500 may end. Method 500 or a partthereof may or may not be repeated, for instance by iterating to anyappropriate stage in method 500. If repeated, the frequency ofrepetition may be dependent on the desired frequency for evaluatingcongestion. Possibly, even if method 500 is not repeated, or betweenrepetitions, one or more stage(s) of method 500 may be performed, forother purpose(s) and/or to maintain routine for observer 470.

Alternatively to the example illustrated in FIG. 5, stages which areshown in as being executed sequentially may in some other examples beexecuted in parallel, and/or stages shown as being executed in parallelmay in some other examples be executed sequentially. Alternatively toany of the example illustrated in FIG. 5, method 500 may in some otherexamples include more, fewer and/or different stages than illustrated.Alternatively to the example illustrated in FIG. 5, stages may in someother examples be executed in a different order than illustrated.

FIG. 6 is a block diagram of an example of an affector system 670, inaccordance with the presently disclosed subject matter. Affector system670 may be configured to affect data in wireless network 100. Affectorsystem 670 may be an example of supervisor system 170 and therefore thedescription of system 670 may not necessarily repeat details describedwith reference to system 170.

In the illustrated example, affector 670 may include a recognizer module672, a noter module 674, a delay evaluator module 676, a delayer module678, a handler module 680, a queue(s) module 684, and optionally a datastructure module 682. Modules 672, 674, 676, 678, 680, 682 and/or 684may be examples of modules 272, 274, 276, 278, 280, 282 and/or 284respectively. Any module in affector 670 may be made up of anycombination of software, hardware and/or firmware suitable for thefunction(s) attributed to the module herein. For example, affectorsystem 670 or any part thereof may include a computer.

Handler module 680, for instance, may be configured to handle datapackets. For instance, a data packet en route from PDN 190 to basestation 130 may be intercepted by handler 680 and subsequently forwardedby handler 680 in order that the data packet may continue to basestation 130 or PDN 190. Alternatively, a data packet en route from PDN190 to base station 130 may not be handled by handler 680. For instancethe data packet may not necessarily be handled if the packet is not tobe delayed. Depending on the instance, a data packet en route from basestation 130 and PDN 190 may or may not be handled.

For instance recognizer 672 may be configured to recognize one or morecharacteristic(s) of a data packet. The subject matter does not limithow recognizer 672 may recognize characteristic(s) of a data packet. Forthe purpose of illustration only, however, some examples are nowpresented.

For example, one or more characteristic(s) may be recognized using deeppacket inspection.

Additionally or alternatively, for example, one or morecharacteristic(s) may be recognized from the header(s) of the datapacket. For instance, depending on the example any of sequence number,type of data packet, tunnel identifier, destination address, sourceaddress, destination port, source port etc may be recognized fromheader(s) of the data packet. Additionally or alternatively, forinstance, the layer 7 header may indicate the type of user traffic suchas browsing, streaming video, streaming audio, downloading, etc.Additionally or alternatively, for instance, for a data packet which isan acknowledgement data packet such as in a reliable protocol, e.g. TCPa possible characteristic may be the acknowledgement number whichenables correspondence to corresponding data packet(s) for which theacknowledgement data packet is acknowledging receipt.

Additionally or alternatively, for example, one or morecharacteristic(s) may be recognized at least partly based on previoussignaling in wireless network 100. For instance, possibly a group(served by a wireless transmitter) and/or base station identifier and/orUE identifier may have been determined from previous signaling. Thesignaling may have included, for instance, a Service Area Identifier (orthe equivalent) which may be used to identifier a service areacomprising one or more groups served by one or more wirelesstransmitters in the same location area and may therefore be consideredto be an example of a group (served by a wireless transmitter) and/orbase station identifier. The signaling may have additionally oralternatively included, for instance, a permanent Non-Access Stratum UEidentity (or equivalent) which may be considered to be an example of aUE identifier. A group (served by a wireless transmitter) and/or basestation identifier and/or a UE identifier may have been stored in anaccessible location to recognizer 672, perhaps in association with anassociated identifier (e.g. tunnel identifier, destination address,source address, destination port, and/or source port etc) which may beincluded in a data packet header, so that recognizer 672 may recognizethat the data packet relates to a certain group served by a wirelesstransmitter, base station, and/or UE at least partly based on the storedidentifier(s). For instance, recognizer 672 may thereby recognize UE 110for which the data packet is destined or from which the data packetoriginated. Additionally or alternatively, for instance, recognizer 672may thereby recognize the group served by a wireless transmitter and/orbase station 130 associated with UE 110 for which the data packet isdestined or from which the data packet originated.

Noter 674 may, for instance, be configured to note a time associatedwith a data packet en route from PDN 190 to base station 130, forinstance any of the time the data packet passes noter 675 (e.g. withouthandling), the time the data packet is intercepted by handler 680, thetime the data packet is forwarded by handler 680, etc. Additionally oralternatively, noter 674 may for instance, be configured to note a timeassociated with a data packet en route from base station 130 to PDN 190,for instance any of the time the data packet passes noter 674 (e.g.without handling), the time the data packet is intercepted by handler680, the time the data packet is forwarded by handler 680, etc. The datapacket traveling in either direction may or may not be anacknowledgement data packet. For instance if a TCP protocol is beingused, an acknowledgement data packet may be sent to acknowledge receiptfor any bytes prior to a certain sequence number. For instance, in somecases, noter 674 may note a first time associated with a particular(non-acknowledgement) data packet traveling from PDN 190 to base station130 and note a second time associated with an acknowledgement datapacket traveling from base station 130 to PDN 190 which acknowledges theparticular data packet, in a manner which imparts that there is arelationship between both times (and/or imparts that there is arelationship between both times and the particular (non acknowledgement)data packet).

Additionally or alternatively, noter 674 may for instance, be configuredto note one or more characteristic(s) recognized by recognizer 672. Forinstance, noter 674 may in some cases reference one or more notedtime(s) to any of a sequence number, UE identifier, group (served by awireless transmitter) and/or base station identifier, data packet type,etc.

Noter 674 may, for instance, be configured to note times and/orcharacteristics in a data structure. The data structure may be locatedin affector 670, e.g. data structure 682 when included, or may belocated externally to affector 670 but in a location accessible to noter674 and/or delay evaluator 676. Additionally or alternatively, noter 674may note the times and/or characteristics to evaluator 676 for use byevaluator 676 without necessarily storing times and/or characteristicsin a data structure.

Delay evaluator 676 may, for instance, be configured to evaluate whetheror not to adjust delaying, e.g. whether or not to delay data packet(s)and/or whether or not to stop delaying data packet(s). Herein, the termdelay may refer to a delay which is for a finite period of time, or foran infinite period of time. For instance, a packet may be delayed for aninfinite period of time by dropping the packet, and the dropping mayoccur after first delaying the packet for a finite period of time, ormay occur without first delaying the packet for a finite period of time.

The subject matter does not limit the manner in which delay evaluator676 may determine whether or not to adjust delaying. However for furtherillustration to the reader some examples are now provided. For example,certain UE(s) 110 may be prioritized and therefore data packet(s)destined for those UE(s) 100 may be less likely to be delayed and/ormore likely to have delay thereof stopped. Additionally or alternativelyfor example, certain data packet type(s) may be prioritized andtherefore data packets of those type(s) may be less likely to be delayedand/or more likely to have delay thereof stopped. Additionally oralternatively, for example it may be determined to delay data packet(s)in order to shorten the queuing time (where the shortened queuing timemay be zero or longer) in base station 130, e.g. so that data packet(s)arriving at base station 130 do not have to wait as long. Continuingwith this example, the time for a certain data packet to travel from PDN190 to UE 110 may be reduced, for instance, if one or more other datapackets are delayed so as to shorten the base station queuing time.Additionally or alternatively, for example it may be determined to notdelay and/or stop delaying data packet(s) in order to increase thequeuing time in base station 130 (from zero or any other queuing timevalue), e.g. so that there may be a minimum number of data packets inbase station 130 at a time. Additionally or alternatively, for exampleit may be determined to adjust delaying in order to attempt to obtaincertain circumstance(s). Some examples of stages which delay evaluator676 may perform to evaluate whether or not to delay data packets aredescribed below with reference to FIG. 7.

Queue(s) 684 may include one or more (data packet) queue(s) where datapacket(s) may be queued. The subject matter does not limit the number ortype of queue(s) 684. However for further illustration some examples arenow provided. For example, the number and/or type of queues 684 may beset based on the desired basis for prioritization. Additionally oralternatively, for example, there may be separate queue(s) 684 for eachUE 110, or any queue 684 may include data packet(s) destined for one ormore UEs 110. Additionally or alternatively, there may be separatequeue(s) 684 for each data packet type or for each collection of datapacket types, or any queue 684 may include data packet(s) of any type.Continuing with this example, there may for instance be two collectionsof data packet types, with one collection including data packet type(s)for which a high quality of experience for the user may depend on datapackets of such type(s) being delivered to the corresponding UE 110 at aconstant rate (e.g. streaming media such as video and/or audio, etc.),and another collection including data packet type(s) for which a highquality of experience for a user may be less likely to depend on datapackets of such type(s) being delivered to the corresponding UE 110 at aconstant rate (e.g. browsing and/or downloading, etc).

Delayer 678 may, for instance, be configured to adjust delaying. Forexample, delayer 678 being configured to adjust delaying may includebeing configured to delay data packet(s), e.g. in queue(s) 682 and/or bydropping, for instance depending on a result of the evaluation by delayevaluator 676. Additionally or alternatively, for example delayer 678being configured to adjust delaying may include being configured to stopdelaying packet(s), e.g. by removing those data packet(s) from queue(s)682, for instance depending on a result of the evaluation by delayevaluator 676.

Alternatively to the example shown in FIG. 6, system 670 may in someexamples include fewer, more and/or different modules than shown in FIG.6. Alternatively to the example shown in FIG. 6 the functionality ofsystem 670 may in some examples be divided differently among the modulesillustrated in FIG. 6. Therefore any function attributed to a certainmodule in an example herein may additionally or alternatively beperformed by different module(s). Alternatively to the example shown inFIG. 6, the functionality of system 670 described herein may in someexamples be divided into fewer, more and/or different modules than shownin FIG. 6. Alternatively to the example shown in FIG. 6, system 670 mayin some examples include additional, less, and/or differentfunctionality than described herein. For example, system 670 may includefunctionality unrelated to affecting data in wireless network 100.

FIG. 7 is a flowchart of an example of an affecting method 700 inaccordance with the presently disclosed subject matter. Affecting method700 may be performed for example by affector 670. Affecting method 700may be used for instance, for affecting data in wireless system 100.Affecting method 700 may be an example of supervision method 300 andtherefore the description of method 700 may not necessarily repeatdetails described with reference to method 300.

In the illustrated example, in optional stage 705, one or more factorsrelating to method 700 may be determined, by affector 670, for instanceby delay evaluator 676. Factor(s) may be determined by way of receivedinput, e.g. from an operator (via an input device such as a keypad,keyboard, mouse and/or any other input device) and/or from an externalelement (external to affector 670) such as a planning tool, databaseand/or any other element. Additionally or alternatively, factor(s) maybe determined based on experience and/or applicable condition(s) (e.g.any of current time of day, location of base station 130, etc). Stage705 may be an example of stage 305.

The subject matter does not limit the factor(s) which may optionally bedetermined in stage 705, but for the sake of further illustration to thereader, some instances will now be presented. For instance, factor(s)may include any of the following: the length of time interval betweentimes of evaluating whether or not to adjust delaying, serviceparameter(s), one or more threshold(s), how to determine threshold(s)which may at least partly depend on current condition(s),circumstance(s) under which to evaluate whether or not to adjustdelaying, number of queue(s), type(s) of queue(s), whether or not delayadjustment should uniformly affect data packet(s), prioritizationscheme(s), initial adjustment variable(s) (if not constant butconfigurable), how to update an adjustment variable (if not constant),constant adjustment variable (if constant and configurable), minimumvalue for adjustment variable (if not constant but configurable), a timeduration, and/or minimum rate per type of data packet for high qualityof experience, etc.

In the illustrated example, in optional stage 715, a data packettraveling from PDN 190 to base station 130) may be handled by affector670, e.g. by handler 680 by intercepting and subsequently forwarding thepacket (e.g. after stage 720). A data packet travelling from basestation 130 to PDN 190 may be handled by affector 670, e.g. by handler680 by intercepting and subsequently forwarding the packet (e.g. afterstage 720). Stage 715 may be an example of stage 315. Alternatively,stage 715 may be omitted if the data packet is not handled.

In the illustrated example, in stage 720, characteristic(s) of the datapacket may be recognized by affector 670, for instance by recognizer672. For instance, characteristic(s) may be recognized using deep packetinspection, from packet header(s), and/or at least partly based onearlier signaling, etc. Stage 720 may be an example of stage 320.

In the illustrated example, in stage 725, affector 670, for instancenoter 674, may note one or more time(s) associated with a data packetand/or recognized characteristic(s). For instance, for a packet en routefrom PDN 190 to base station 130 the time that the data packet passesthe location of noter 674 (e.g. without handling), the time the datapacket is intercepted, or the time the data packet is forwarded may benoted. Possibly, if there is a corresponding acknowledgement data packeta time for the corresponding acknowledgement packet such as the time theacknowledgement packet passes the location of noter 274 (e.g. withouthandling), the time the data packet is intercepted, or the time the datapacket is forwarded may be noted, e.g. with reference to thecorresponding data packet which travelled in the direction from PDN 190to base station 130. Stage 725 may be an example of stage 325.

Depending on the instance, stages 715 to 725 may be performed fordifferent data packets in parallel, or the stages may be completed forone data packet before being performed for another data packet.

In the illustrated example, in stage 726 it may he determined byaffector 670, for instance by delay evaluator 676 whether or not it istime to evaluate delay adjustment. For instance, the length of the timeinterval from the last evaluation may have been determined in stage 705.If it is not time to evaluate (no to stage 726) then method 700 iteratesto stage 715 and continues to handle data packets without evaluation.

If it is time to evaluate (yes to stage 726) then in the illustratedexample in optional stage 730, an adjustment variable may be updated byaffector 670, e.g. by delay evaluator 676. For instance, assume that aservice parameter for user equipment 110 for which the data packet isdestined is at least partly dependent on the time noted for the datapacket traveling to user equipment 110 and the time noted for thecorresponding acknowledgement data packet. (If the acknowledgement datapacket acknowledged more than one data packet, it is assumed forsimplicity of description that the noted time is the time associatedwith the last acknowledged data packet. However in other examples thetime may be a function of the times associated with the acknowledgeddata packets, mutatis mutandis). The difference between the time notedfor the data packet travelling in the direction toward user equipment110 and the time noted for the corresponding acknowledgement data packetmay be caused by one or more causes, and may not necessarily be solelydue base station queuing time (e.g. time between when the data packetarrived at base station 130 and when the data packet left base station130 on the way to user equipment 130 which may reflect the serviceprovided by base station 130 to user equipment 110.) Cause(s) unrelatedto the base station queuing time may include cause(s) related to thebase station (but not to the base station queuing time) and/or cause(s)unrelated to the base station. Depending on the instance, any cause(s)unrelated to the base station queuing time may be ignored, or anadjustment variable may be estimated in order to attempt to adjust forthese other cause(s). The adjustment variable associated with a specificparameter may be particular to user equipment 110 or may be common toone or more group(s) served by one or more wireless transmitter(s).

The subject matter does not limit how the adjustment variable may beupdated, but for the sake of further illustration to the reader, aninstance is now provided.

Consider that the adjustment variable is trying to estimate the minimumperiod between when a certain data packet traveling toward UE 110 wouldpass or be handled by affector 670 and a corresponding acknowledgementpacket would pass or be handled by affector 670 when there would bepractically no queuing time between the time of arrival of the certaindata packet at base station 130 and time of leaving of the certain datapacket from base station 130, and therefore the length of the periodwould be dependent on cause(s) other than the base station queuing time.Such an adjustment variable is also termed “round trip time adjustment”herein. For instance such an adjustment variable may be initiallyupdated (set) to a value such as 10 or 20 ms. The adjustment variablemay be reset to such a value, for instance any time wireless network 100is reconfigured (e.g. adding, changing, and/or deleting an element inwireless network 100). The adjustment variable may optionally be updatedby slowly being increased (e.g. 1 ms per hour). However, if thedifference between the time noted for a data packet traveling to userequipment 110 and the time noted for the corresponding acknowledgementdata packet is less than the current adjustment variable, the adjustmentvariable may be updated to equal difference minimum value (e.g. initialvalue) so as to reflect a minimum period. If the adjustment variable isspecific to a particular user equipment, then the adjustment variablemay be updated to the minimum value only if the difference relates tothat user equipment 110, but if the adjustment variable is common to oneor more group(s)served by one or more wireless transmitter(s), then theadjustment variable may be updated to the minimum value provided thedifference relates to any user equipment associated with any of thesegroup(s) served by wireless transmitter(s).

Although the updating in stage 730 may occur at any time, as describedabove, for simplicity of illustration, stage 730 is illustrated afterstage 726. Stage 730 may be an example of stage 330.

In some examples, stage 730 may be omitted, for instance if cause(s) notdirectly related to base station 130 may be ignored, or if an adjustmentvariable may not easily and/or reliably be determined. In some of theseother examples where stage 730 may be omitted, the adjustment variablemay be a constant configurable value.

In the illustrated example, in optional stage 731, it may be checked byaffector 670, for instance by delay evaluator 676, whether or notcertain circumstance(s) exist. For instance, in some cases it may bepreferable to perform an evaluation if certain circumstance(s) exist.The subject matter does not limit the circumstance(s) but for the sakeof further illustration to the reader some instances are now presented.

For instance, estimation of a parameter relating to the base stationoutgoing rate from base station 130 may possibly be facilitated when theround trip time or a function thereof is steady. The round trip time maybe estimated as the difference between the time noted for a data packettraveling to user equipment 110 and the time noted for the correspondingacknowledgement data packet. The round trip time or a function thereofmay be considered as indicative of the queuing time in base station 130.Therefore, if the round trip time or a function thereof (e.g. round triptime minus round trip time adjustment) is steady, the base stationoutgoing rate may be estimated as being approximately equal to theincoming rate to base station 130. A base station outgoing rate may bean outgoing rate from base station 130 to any one of a plurality of userequipments 110 or an outgoing rate from base station 130 to theplurality of user equipments. In this case, a steady round trip time orfunction thereof may be a circumstance that is checked for. The subjectmatter does not limit for how long the round trip or function thereofshould be steady.

Additionally or alternatively, for instance, estimation of a parameterrelating to a particular UE 110 whose service may be affected by otherUEs 110 competing for service (for instance dependent on a schedulingalgorithm of a scheduler in base station 130), may possibly befacilitated when the other UEs 110 are not being serviced, so as toreduce the effect of service to other UEs 110 on the parameter relatingto the particular UE 110 and/or to focus on reason(s) relatingspecifically to the particular UE 110 (such as reception conditions). Inthis case, non-service to competing UEs 110 may be a circumstance thatis checked for. Continuing with this case, there may be a check for aparameter indicative of service provision to only one (or to more thanone) of these UEs 110.

In the illustrated example, in optional stage 732, if it may bedetermined that the checked for circumstance(s) exist(s) (yes to stage732) then method 700 may proceed to stage 735. If instead it may bedetermined that the checked for circumstance(s) do not exist (no tostage 732) then method 700 may proceed to stage 733.

In the illustrated example in optional stage 733, affector 670, forinstance delay evaluator 676, may wait until the certain circumstance(s)may be met (for a particular evaluation) and/or may instruct delayer 678to adjust delaying in order to obtain certain circumstance(s) (for aparticular evaluation) which delayer 678 may then do.

For instance, assume that initially data packets traveling toward basestation 130 are handled by affector 670 but there is no delay in datapackets and therefore the rate out of affector 670 (which may beapproximated as the incoming rate to base station 130) substantiallyequals the rate into affector 670, e.g. with First In First Out (FIFO).Further assume that based on noted times, an average round trip time orfunction thereof for a plurality of UEs 110 (e.g. associated with one ormore group(s) served by one or more wireless transmitter(s)) may bedetermined, and it is perceived that the average is increasing. In orderto attempt obtaining a steady average round trip time or functionthereof, (disregarding type of packet or destination UE 110 forsimplicity of description), delayer 678 may delay data packets for anyof these UEs 110 intercepted by handler 680, for instance by droppingpacket(s) and/or by placing the intercepted packets in queue(s) 684,e.g. continuing to use FIFO but decreasing the rate out of affector 670until a steady average round trip time or function thereof is obtained.

Additionally or alternatively, for instance, in order to bring aboutnon-service to all but one of competing user equipment(s) 110, affector670 may intercept data packet(s) destined for any other competing userequipment(s) 110 and delay the packet(s) (e.g. by dropping datapacket(s) and/or placing the data packet(s) in queue(s) 684). Forinstance, affector 670 may determine that there is a parameterindicative of data packets being provided by base station to more thanone of the competing user equipments 110, and delay packet(s), in orderto bring about non-service to all but one of competing user equipments110.

When performed, the performance of stages 731 to 733, may optionallyinclude estimation of a parameter (e.g. round trip time, adjusted roundtrip time, and/or a parameter indicative of service provision to onlyone [or to more than one] of competing user equipments 110, etc),determining at least partly based on the estimated parameter whether ornot to adjust delaying, and adjusting delaying if determined to do so.

In the illustrated example after stage 733, method 700 iterates to stage731.

In some instances, stages 731 to 733 may be omitted, for instance ifthere is no advantage to performing an evaluation under certaincircumstance(s). Additionally or alternatively, if more than oneevaluation is performed, of which for part there is an advantage and foranother part there is not advantage, then stages 731 to 733 may beperformed before the part for which there is an advantage, whereas theother part may be performed without first performing stages 731 to 733.

In the illustrated example, in stage 737, a service parameter may beestimated for an individual user equipment 110 (e.g. any one of aplurality of user equipments 110). A service parameter estimated for anindividual user equipment 110 may provide some sort of indication of theservice that is being provided to that user equipment 110. Possibly aservice parameter may be negatively affected by queuing time in basestation 130, and in this case the parameter may be considered indicativeof base station queuing time. Additionally or alternatively, a serviceparameter may be estimated for a plurality of user equipments 110 byaffector 670, for instance by delay evaluator 276. Stage 737 may be anexample of stage 337. The subject matter does not limit the estimatedservice parameter, but for the sake of further illustration to thereader, some instances are now provided.

For instance, a possible service parameter for an individual UE 110 mayestimate a round trip time (e.g. the difference between the time notedfor the current data packet traveling to the individual user equipment110 and the time noted for the corresponding acknowledgement datapacket). Additionally or alternatively, for instance a possible serviceparameter for an individual UE 110 may estimate a function (e.g.average, sum, etc) of a plurality of round trip times, e.g. with eachround trip time e.g. reflecting the time noted for a certain data packettraveling to the individual user equipment 110 and the time noted forthe corresponding acknowledgement data packet. For instance,additionally or alternatively, a possible service parameter for anindividual UE 110 may estimate an adjusted round trip time (e.g. roundtrip time minus a round trip time adjustment). Additionally oralternatively, for instance a possible service parameter for anindividual UE 110 may estimate a function (e.g. average, sum, etc) of aplurality of adjusted round trip times, with each round trip time e,greflecting a round trip time and round trip time adjustment.Additionally or alternatively, for instance, a possible serviceparameter for an individual UE 110 may be indicative of base stationqueuing time. Additionally or alternatively, for instance, a possibleservice parameter for an individual UE 110 may be a function (e.g.average, sum, etc.) of parameters indicative of base station queuingtimes. Additionally or alternatively, for instance, a possible serviceparameter for an individual UE 110 may estimate a base station outgoingrate (e.g. the difference between two times noted for two differentacknowledgement packets, not necessarily sequential, from the individualUE 110 divided by the difference between the noted sequence numbers). Itis noted that since an outgoing rate may rely on acknowledgement packetswhich are not necessarily sequential, meaning not necessarily followingone another in order, an outgoing rate may possibly be calculated evenwhen intervening packet(s) relate to a protocol which is not necessarilyreliable, e.g. User Datagram Protocol (UDP). Additionally oralternatively, for instance, a possible service parameter for anindividual UE 110 may estimate a function (e.g. average, sum, etc) of aplurality of outgoing rates, with each outgoing rate e.g. reflecting twotimes noted for acknowledgement packets and sequence numbers.Additionally or alternatively, for instance, a possible serviceparameter for an individual UE 110 may estimate a quotient for a roundtrip time or adjusted round trip time divided by the difference betweenan outgoing rate and an incoming rate to base station 130. Additionallyor alternatively, for instance, a possible service parameter for anindividual UE 110 may estimate a function (e.g. average, sum, etc) of aplurality of quotients. If times were already noted for a plurality ofpackets destined to the individual UE 110 (e.g. since the last time ofevaluation), then a possible service parameter may reflect the pluralityof packets, a subset of the packets or even only one or two (e.g. last)of the packets.

It is noted that even though a service parameter may be estimated for aparticular user equipment 110, the service parameter may be affected bythe service provided to other user equipments 110. For instance,assuming other user equipment(s) 110 may be associated with any of oneor more group(s) served by one or more wireless transmitter(s), whichcompete for service with particular user equipment 110. Further assumingthat base station 130 includes a scheduler which does not want to alwaysstarve all of these other user equipment(s) 110, then the serviceparameter for particular user equipment 110 may possibly at leastsometimes reflect a poorer service than if only the particular userequipment 110 was being serviced. As mentioned above, under certaincircumstance(s), a service parameter may optionally be preferablyestimated when no other competing UEs 110 are being serviced.

Assume that additionally or alternatively a possible service parametermay be estimated for a plurality of user equipments 110. Such a serviceparameter may provide some sort of indication of the service that isbeing provided to the plurality of user equipments 110. Possibly aservice parameter may be negatively impacted by the queuing time in basestation 130 for data packet(s) destined for any of the plurality of UE110, and in this case the parameter may be considered indicative of basestation queuing time.

For instance, a possible service parameter estimated for a plurality ofequipments 110 may include a function (e.g. average, sum, etc) ofservice parameters for individual user equipments 110 included in theplurality. For example, a possible service parameter for a plurality ofuser equipments may be estimated as an average of round trip times orfunctions thereof (e.g. round trip time minus round trip timeadjustment) for various user equipments 110 included in the plurality.An average may reflect for instance any data packet(s) destined for anyuser equipment(s) 110 included in the plurality with time(s) noted sincethe last time of evaluation, may reflect a subset of the packets withtime(s) noted since the last time of evaluation, or may only reflect oneor two packets (e.g. last) with time(s) noted since the last time ofevaluation for any user equipment 110 included in the plurality.Additionally or alternatively, for instance, a possible serviceparameter estimated for a plurality of user equipments 110 may notnecessarily include a function of service parameters for individual userequipments 110 included in the plurality. For example a possible serviceparameter for a plurality of user equipment may include a parameterindicative that service is currently being provided by base station 130to only one of the plurality of UEs 110, and/or a base station outgoingrate to the plurality of user equipments 110, etc.

As mentioned above, a base station outgoing rate for a particular UE 110or fur a plurality of UEs 110 may possibly be estimated when there is asteady round trip time or function thereof. For instance, for a basestation outgoing rate for a particular UE 110, once a round trip time orfunction thereof for a particular UE 110 is steady, the outgoing ratefor the particular UE 110 may be estimated by affector 670, forinstance, as approximately equaling the incoming rate to base station130 of data packet(s) destined for the particular UE 110. The incomingrate may be approximated, say, as approximately equaling the rate thatdata packet(s) destined the particular UE 110 pass by and/or areforwarded by affector 670. The rate in which the packet(s) pass byand/or are forwarded may be determined, e.g. from noted times.Similarly, for a base station outgoing rate for a plurality of UEs 110,once the average round trip time or function thereof is steady, the basestation outgoing rate may be estimated by affector 670, for instance, asapproximately equaling the incoming rate to base station 130 of packetsdestined for any of the plurality of user equipments 110. The incomingrate may be approximated, say, as approximately equaling the rate thatdata packet(s) destined for any of the plurality of UEs 110 pass byand/or are forwarded by affector 670. The rate in which the packet(s)pass by and/or are forwarded may be determined, e.g. from noted times.

In the illustrated example, in optional stage 742, a threshold may bedetermined by affector 670, for instance by delay evaluator 676, forcomparison with a service parameter. Possibly, a threshold may be atleast partly dependent on current condition(s), and therefore may nothave been determined earlier (e.g. in stage 705). Threshold(s)determined in stage 742 may be the same for all UEs 110, may vary fordifferent UEs 110, may be constant over time, and/or may vary over time,etc. The subject matter does not limit threshold(s) but for the sake offurther illustration to the reader some instances are now presented.

For instance, a threshold may be dependent on a minimum required rate toenable a high quality of user experience for types of data packet(s)provided to a UE 110 or to a plurality of UEs 110. Assume, e.g. that instage 725, the types of data packets may be noted. Possibly a minimumrate per type of data packet may have been determined e.g. in stage 705,in order to determine a threshold dependent on a minimum required ratefor a particular UE 110, affector 670 may e.g. add up a minimum rate pertype of data packet recently noted for that UE 110. Additionally oralternatively in order to determine a threshold dependent on a minimumrequired rate for a plurality of UEs 110, affector 670 may e.g. add upthe minimum rate per type of data packet recently noted for any UE 110in that plurality of UEs 110. The subject matter does not limit thedefinition of “recently”, and may include any duration, typicallyalthough not necessarily of shorter length than the interval since thelast evaluation time.

Stage 742 may be omitted in some instances, or if there is a pluralityof iterations of stage 749 with different threshold, stage 742 may beperformed for part of the thresholds but not for another part. Anythreshold, not necessarily partly dependent on current condition(s), mayhave been determined earlier or may be determined in stage 742. Such athreshold may be the same for all UEs 110, may vary for different UEs110, may be constant over time, and/or may vary over time, etc. Thesubject matter does not limit such a threshold but for the sake offurther illustration to the reader some instances are now presented.

For instance, an example of a threshold which may have been determinedearlier or during stage 742 may be a threshold dependent on the lengthof the time interval between evaluations. Additionally or alternatively,for instance, another example of a threshold which may have beendetermined earlier or during stage 742 may be a threshold indicative ofmaximum desired base station queuing time For instance, the maximumdesired base station queuing time may be a queuing time which isconsidered low enough to allow packets prioritized by affector 670 tonot wait too long in base station 130, where the designation of what is“not too long” is not limited by the subject matter.

In the illustrated example, in stage 749, an estimated service parametermay be compared to a threshold by affector 670 e.g. by delay evaluator676. Stage 749 may he an example of stage 349. In the illustratedexample, in stage 765, at least partly based on this estimated parameteraffector 670, for instance delay evaluator 676, may determine whether ornot to adjust delaying of at least one data packet. Stage 765 may he anexample of stage 365. The determining may or may not be at least partlybased on quality of experience considerations. If based at least partlyon quality of experience considerations, the subject matter does notlimit the considerations nor how such considerations may be taken intoaccount in the determining, but for the sake of further illustration tothe reader some examples are presented in the description herein ofmethod. 700 with reference to thresholds, prioritization schemes, etc.

The subject matter does not limit how the estimated parameter may betaken into account in the determining. For instance, the determining maypossibly take into account a relationship between parameter andthreshold. The subject matter does not limit the estimated parameter,threshold, and/or manner of determining, but for the sake of furtherillustration to the reader, some instances are now presented.

For instance, there may be a plurality of competing user equipment(s)110 which compete for service by base station 130. A scheduler in basestation 130 may determine how to schedule the data packets. Forsimplicity's sake assume the plurality of competing user equipment(s)110 may be associated with any of one or more group(s) served by one ormore wireless transmitter(s). The associated group(s) may or may not beall of the group(s) serviced by base station 130. Assume further that instage 725 for any data packet a group/base station identifier and a UEidentifier are noted (or if affector 670 only notes packets for thegroup(s)/base station then the group/base station identifier may notnecessarily be noted). Affector 670, e.g. delay evaluator 676 may noticethat for a given UE 110 (out of the plurality of competing UEs 110)between the noted time a certain packet destined for the given UE 110passed by or was forwarded by affector 670 and the time noted for anacknowledgement of a subsequent (but not necessarily sequential) packetdestined for UE 110, there were no packets for any other competing UEs110. For instance, any noted passing by or forwarding time of a packetdestined for another competing UE 110 as well as the noted time for thecorresponding acknowledgement may have been before the noted forwardingor passing by time of the certain packet. Additionally or alternativelyfor instance, any noted passing by or forwarding time of a packetdestined for another competing UE 110 may have been after theacknowledgement time for the subsequent packet for given UE 110. Thebase station outgoing rate for the given UE 110 when there is nocompetition may therefore be estimated as the difference between thenoted acknowledgement time of the subsequent packet and the notedacknowledgement time of the certain packet divided by the differencebetween the respective noted sequence numbers. This rate may beindicative of reception conditions for given UE 110. The rate may becompared to a threshold dependent on a minimum required rate for thegiven UE 110 (e.g. comprising a sum of the minimum rate per type of datapacket recently noted for the given UE 110). If the rate is less thanthe threshold, then it may be determined that based on a result of thiscomparison delaying should be adjusted, e.g. by affector 670 delayingone or more packet(s) destined for UE 110. If the rate is already equalto or more than the threshold, then no delay adjustment may be necessarybased on a result of this comparison (although may possibly be necessarybased on a result of another comparison).

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate the average round trip time or a functionthereof (e.g. round trip time less round trip time adjustment) for aplurality of user equipments 110 and determine that the average issteady. Delay evaluator 676 may then estimate that the outgoing ratefrom base station 130 to the plurality of UEs 110 may be approximatelyequal to the incoming rate to base station 130 for the plurality of UEs110 which in turn may be approximately equal to the rate of forwardingand/or passing by affector 670 for the plurality of UEs 110. Forinstance, if there is no differentiation between the various userequipments 110 in the plurality of user equipments 110 the passingby/forwarding rate may be determined based on noted passingby/forwarding times for packets destined for any of the plurality ofuser equipments 110. Assuming the type(s) of data packets destined forany of these plurality of equipments have been noted, this rate may becompared to a threshold dependent on a minimum required rate fir theplurality of UEs 110 (e.g. comprising a sum of the minimum rate per typeof data packet recently noted for any of the plurality of UEs 110). Ifthe rate is less than the threshold, then it may be determined thatbased on a result of this comparison delaying should be adjusted, e.g.by delaying one or more packet(s) destined for any of the plurality ofUEs 110 in affector 670. If the rate is already equal to or more thanthe threshold, then no delay adjustment may be necessary based on aresult of this comparison (although may possibly be necessary based on aresult of another comparison). The plurality of user equipments 110 mayor may not compete for service and/or may or may not be associated withone or more group(s) served by one or more wireless transmitters (s) ofbase station 130,

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate a parameter indicative of base stationqueuing time in base station 130 (e.g. round trip time or adjusted roundtrip time) for any individual user equipment 110. If it may be assumedthat there is a time interval between evaluation times, meaning that theparameter may be estimated after an interval from the last estimation,delay evaluator 676 may compare the parameter to a threshold dependenton the length of the time interval. If the parameter is shorter than thethreshold then affector 670 may determine to adjust delaying (e.g. bystopping delaying at least one packet destined for individual UE 110)and/or may determine not to adjust delaying (e.g. not delaying) at leastone packet destined for individual UE 110 based on a result of thiscomparison. The parameter being shorter than the threshold may beindicative of too short base station queuing time, where the definitionof “too short” is not limited by the subject matter but may mean thatthat base station 130 may not be sufficiently occupied with servicingindividual UE 110 and/or that power consumption may be too high. Forinstance, the adjustment may attempt to cause the parameter indicativeof base station queuing time (e.g. e.g. round trip time or adjustedround trip time) to be at least equal to the length of the interval sothat base station 110 may be sufficiently occupied with individual UE110 and/or to improve power consumption. If the parameter is alreadyequal to or longer than the threshold, then affector 670 may determinethat stopping delaying and/or not delaying may not be necessary based ona result of this comparison (although may possibly be necessary based ona result of another comparison).

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate a parameter indicative of base stationqueuing time (e.g. average round trip time or average adjusted roundtrip time) for a plurality of user equipments 110. If it may be assumedthat there is a time interval between evaluation times, meaning that theparameter may be estimated after an interval from the last estimation,delay evaluator 676 may compare the parameter to a threshold dependenton the length of the time interval. If the parameter is shorter than thethreshold, then affector 670 may determine to adjust delaying (e.g. bystopping delaying of at least one packet destined for any of theplurality of user equipments 110) and/or may determine not to adjustdelaying (e.g. not delaying) at least one packet destined for any of theplurality of user equipments 110 based on a result of this comparison.The parameter being shorter than the threshold may be indicative of tooshort base station queuing time, where the definition of “too short” isnot limited by the subject matter but may mean that that base station130 may not be sufficiently occupied with servicing the plurality of UEs110 and/or that power consumption may be too high. For instance, theadjustment may attempt to cause the parameter indicative of base stationqueuing time (e.g. average round trip time or adjusted round trip time)to be at least equal to the length of the interval so that base station110 may be sufficiently occupied with the plurality of UEs 110 and/or toimprove power consumption. If the parameter is already equal to orlonger than the threshold, then affector 670 may determine that stoppingdelaying and/or not delaying may not be necessary based on a result ofthis comparison (although may possibly be necessary based on a result ofanother comparison). The plurality of user equipments 110 may or may notcompete for service and/or may or may not be associated with one or moregroup(s) served by one or more wireless transmitter(s) of base station130.

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate a plurality of parameters indicative of basestation queuing time (e.g. round trip time or adjusted round trip time),each for one UE 110 in a plurality of user equipments 110. If it may heassumed that there is a time interval between evaluation times, meaningthat each of these parameters may be estimated after an interval fromthe last estimation, delay evaluator 676 may compare each of theseparameters to a threshold dependent on the length of the time interval.If for a predetermined percentage of comparisons the parameter isshorter than the threshold, then affector 670 may determine to adjustdelaying (e.g. by stopping delaying of at least one packet destined forany of the plurality of user equipments 110) and/or may determine not toadjust delaying (e.g. not delaying) at least one packet destined for anyof the plurality of user equipments 110 based on a result of thiscomparison. The parameter being shorter for a predetermined percentageof comparisons may be indicative of too short base station queuing time,where the definition of “too short” is not limited by the subject matterbut may mean that base station 130 may not be sufficiently occupied withservicing the plurality of UEs 110 and/or that power consumption may betoo high. For instance, the adjustment may attempt to cause for apredefined percentage of UEs 110 the respective parameter indicative ofbase station queuing time (e.g. round trip time or adjusted round triptime) to at least equal the length of the interval so that base station110 may be sufficiently occupied with the plurality of UEs 110 and/or toimprove power consumption. If, for the predefined percentage, therespective parameter is already equal or longer than the threshold, thenaffector 670 may determine that stopping delaying and/or not delayingmay not be necessary based on a result of this comparison (although maypossibly be necessary based on a result of another comparison). Theplurality of user equipments 110 may or may not compete for serviceand/or may or may not be associated with one or more group(s) served byone or more wireless transmitters (s) of base station 130.

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate a parameter indicative of base stationqueuing time (e.g. round trip time or adjusted round trip time) fir anyuser equipment 110. Delay evaluator 676 may compare this parameter to athreshold dependent on a maximum desired base station queuing time. Ifthe parameter is longer than the threshold, then affector 670 maydetermine to adjust delaying (e.g. by delaying at least one packet forUE 110) based on a result of this comparison. The parameter being longerthan the threshold may be indicative of too long base station queuingtime, where the definition of “too long” is not limited by the subjectmatter. For instance, the adjustment may attempt to cause the parameterindicative of base station queuing time (e.g. round trip time oradjusted round trip time) to not exceed the maximum desired base stationqueuing time. If the parameter is already shorter than or equal to thethreshold, then delay adjustment may not be necessary based on result ofthis comparison (although may possibly be necessary, based on a resultof another comparison).

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate a parameter indicative of base stationqueuing time (e.g. average round trip time or adjusted round trip time)for a plurality of user equipments 110. Delay evaluator 676 may comparethis parameter thereof to a threshold dependent on a maximum desiredbase station queuing time. If the parameter is longer than thethreshold, then affector 670 may determine to adjust delaying (e.g. bydelaying at least one packet for any of the plurality of UEs 110). Theparameter being longer than the threshold may be indicative of too longbase station queuing time, where the definition of “too long” is notlimited by the subject matter. For instance, the adjustment may attemptto cause the parameter indicative of base station queuing time (e.g.average round trip time or adjusted round trip time) to not exceed themaximum desired base station queuing time. If the parameter is alreadyshorter than or equal to the threshold, then delay adjustment may not benecessary based on a result of this comparison (although may possibly benecessary based on a result of another comparison). The plurality ofuser equipments 110 may or may not compete for service and/or may or maynot be associated with one or more group(s) served by one or morewireless transmitter(s) of base station 130.

Additionally or alternatively, for instance, affector 670 e.g. delayevaluator 676 may estimate a plurality of parameters indicative of basestation queuing time (e.g. round trip time or adjusted round trip time),each for one UE 110 in a plurality of user equipments 110. Delayevaluator 676 may compare each of these parameters to a thresholddependent on a maximum desired base station queuing time. If for apredetermined percentage of comparisons the parameter is longer than thethreshold, then affector 670 may determine to adjust delaying (e.g. bystopping delaying of at least one packet destined for any of theplurality of user equipments 110) and/or not delaying at least onepacket destined for any of the plurality of user equipments 110 based ona result of this comparison. The parameter being longer for apredetermined percentage of comparisons may be indicative of too longbase station queuing time, where the definition of “too long” is notlimited by the subject matter. For instance, the adjustment may attemptto cause for a predefined percentage of UEs 110 the respective parameterindicative of base station queuing time (e.g. round trip time oradjusted round trip time) to not exceed the maximum desired base stationqueuing time. If for the predefined percentage the respective parameteris already shorter than or equal to the maximum desired base stationqueuing time, then affector 670 may determine that stopping delayingand/or not delaying may not be necessary based on result of thiscomparison (although may possibly be necessary, based on a result ofanother comparison). The plurality of user equipments 110 may or may notcompete for service and/or may or may not be associated with one or moregroup(s) served by one or more wireless transmitter(s) of base station130.

Depending on the number of parameter(s) which may be estimated, any ofstages 730 to 765 may be performed one or more times. If performed aplurality of times, the adjustment variables, estimated parameters,and/or thresholds from different iterations may relate to the same userequipment(s) 110 (and/or the same plurality of user equipments 110)and/or to different user equipment(s) 110 (and/or to differentpluralities of user equipments 110). If performed a plurality of times,then a final determination of delay adjustment may be made which mayconsider one or more of the various determinations in stage 765 for therespective comparisons and therefore the final determination of whetheror not to adjust delaying may be at least partly based on at least oneparameter estimated during at least one of the plurality of times.

If it is determined to adjust delaying (yes to stage 770), then in theillustrated example, in stage 775 there may be an adjustment of thedelaying by affector 170, for instance delayer 678 and method 700 maythen iterate to stage 715. Stage 770 may be an example of stage 370.Stage 775 may be an example of stage 375. If not (no to stage 770), thenin the illustrated example method 700 may iterate directly to stage 715.

For instance, in stage 775, affector 760, e.g. delayer 678, may adjustdelaying by delaying data packet(s) (e.g. by placing data packets inqueue(s) 684 and/or dropping packet(s)) and/or by stopping delaying ofdata packet(s) (e.g. removing data packet(s) from queue(s) 684), etc.Additionally or alternatively, delayer 678 may not adjust delaying byway of not delaying data packet(s) (e.g. not putting data packet(s) inqueue(s) 684 nor dropping packet(s))). There may be any number and/ortype of queue(s) 684. The number and/or type of queues 684 may or maynot be set based on the desired basis for prioritization. For instance,there may be separate queue(s) 684 for each UE 110, or any queue 684 mayinclude data packet(s) destined for one or more UEs 110; and/or theremay be separate queue(s) 684 for each data packet type or for eachcollection of data packet types, or any queue 684 may include datapacket(s) of any type; etc.

Depending on the example, a determination in stage 770 and optionally asubsequent delay adjustment in stage 775 may or may not be applieduniformly to data packets and therefore may not necessarily affect thedata packets uniformly. For example, a uniform determination to apply adelay adjustment may include delaying each data packet, delaying eachdata packet for a certain amount of time, stopping the delay of eachdata packet, and/or stopping the delay of each data packet after acertain amount of time has passed, etc. For example, a uniformdetermination not to apply a delay adjustment may include not delayingany data packet. For example, a non-uniform determination regardingdelay adjustment may include a data packet prioritization scheme.

In examples where data packets may not be uniformly affected by a delayadjustment, the subject matter does not limit the prioritization scheme.However, for the sake of further illustration to the reader, someexamples are now presented.

For example, in a prioritization scheme non-prioritized data packet(s)may be delayed while prioritized data packet(s) may not be delayed ormay have delay thereof stopped before non-prioritized data packets.

Additionally or alternatively, for example, selection of data packet(s)in a prioritization scheme may be at least partly random, meaning thatcertain data packets may be randomly selected to be prioritized whileothers may be randomly selected to not be prioritized.

Additionally or alternatively, for example, selection of data packet(s)in a. prioritization scheme may be at least partly based on time, forinstance with earlier (or later) data packets selected to be prioritizedand later (or earlier) data packets selected to be non-prioritized.

Additionally or alternatively, for example selection of data packet(s)in a prioritization scheme may be at least partly based on one or moredata packet characteristic(s). The subject matter does not limit theprioritization based on packet characteristic(s). However, for the sakeof further illustration to the reader, some instances are now presented.

For instance, consider the characteristic of data packet type. Assumethat it is determined that a particular UE 110 may not properly receiveall data packets destined for particular UE 110 e.g. due to receptionconditions even when disregarding other competing UEs 110. Possibly, thebase station outgoing rate for particular UE 110 may have been estimatedwhile no other competing UEs 110 were being serviced, as describedabove. If the base station outgoing rate to this particular UE 110 isestimated to be below the minimum rate required for a certain type ofdata packet(s) destined for this UE 110, then it may be determined todelay this type of data. If, however, the outgoing rate is not below anyminimum rate required for any type of data packet destined for this UE110 but is below the sum of minimum rates required for all types of datapackets destined for UE 110, then it may be determined, for instance toprioritize the data packets of type(s) for which a high quality of userexperience depends on a constant rate (e.g. streaming, etc.) and todelay data packet(s) of type(s) for which a high quality of userexperience may not necessarily depend on a constant rate (e.g.downloading and/or browsing, etc.).

Additionally or alternatively, for instance, consider thecharacteristic(s) of data packet type and/or UE 110 identifier. Assumethat it is determined that not all of a plurality of UE's 110 mayproperly receive all data packets destined for these UEs 110. In thisinstance, prioritization may be based on UE 110 and/or type of data. Forexample, assume the first priority is to prioritize data packets oftype(s) for which a high quality of user experience depends on aconstant rate (e.g. streaming, etc). Possibly, the base station outgoingrate for the plurality of UEs 110 may have been estimated as describedabove. If the base station outgoing rate from base station 130 to thisplurality of UEs 110 is estimated to be below the minimum rate requiredto provide a certain type of data packets for which a high quality ofexperience depends on a constant rate to even one UE 110 in thisplurality which is supposed to be provided with this type of data, thenit may be determined to delay this type, even though this type of datais prioritized. If however the outgoing rate to this plurality is atleast equal to the minimum rate required to provide a certain type ofdata packets for which for which a high quality of user experiencedepends on a constant rate to one or more UE(s) 110 in this pluralitywhich is/are supposed to be provided with this type of data, but not toall UEs 110 in this plurality which are supposed to be provided withthis type of data, then based on prioritization of users, this type ofdata may be delayed for certain user equipment(s) 110 but not for otheruser equipment(s) 110(s) in the plurality. If however, the outgoing rateto this plurality is at least equal to the minimum rate required toprovide a certain type of data packets for which a high quality of userexperience depends on a constant rate, to all UEs 110 in this pluralitywhich are supposed to receive this type of data, then this type of datamay be prioritized, and other data packet(s) of type(s) for which a highquality of user experience may not necessarily depend on a constant rate(e.g. downloading, and/or browsing, etc) may be delayed.

Additionally or alternatively, for instance, consider the characteristicof data packet type. Assume that it is determined that the queuing timein base station 130 is too long or too short (e.g. when compared to athreshold) for a particular UE 110. On order to simplify the discussiondisregard any effect from other UEs 110 and/or reception conditions). Ifthe first priority is to prioritize data packets of type(s) for which ahigh quality of user experience depends on a constant rate (e.g.streaming, etc), then if the base station queuing time is too long andit is desired to reduce the queuing time, data packet(s) of othertype(s) may be more likely to be delayed and/or may be less likely tohave delay stopped. However, if the base station queuing time is tooshort and it is desired to increase the queuing time then data packet(s)of type(s) for which a good quality of user experience depends on aconstant rate may be less likely to be delayed and/or more likely tohave delay stopped.

Additionally or alternatively, for instance, consider the characteristicof UE identifier. Assume that it is determined the queuing time in basestation 130 for a plurality of UEs 110 is too long or too short (e.g.when compared to a threshold). If there is no difference in types ofdata packets or collections of data packet types (or for simplicity'ssake disregarding any differences), but there is a difference inprioritization for different users, then if the base station queuingtime is too long (e.g. compared to a threshold) and it is desired toreduce the queuing time, data packet(s) for user equipments 110associated with non-prioritized user(s) may be more likely to be delayedand/or less likely to have delay stopped. However, if the base stationqueuing time is too short and it is desired to increase the queuing timethen data packet(s) for user equipments 110 associated with prioritizeduser(s) may be less likely to be delayed and/or more likely to havedelay stopped.

It is noted that stages 715 to 725 may have continued to be performed asdata packets are handled while stages 726 to 775 were being performed.

In some examples, rather than iterating to stage 715 after stage 770 or715, method 700 may iterate to any other stage in method 700 or may end.If ended, or between iterations, it may still be possible that one ormore stage(s) of method 700 may be performed, for other purpose(s)and/or to maintain routine for affector 670.

In some instances, the time period for a particular data packet totravel from PDN 190 to UE 110 may be reduced due to the delay of one ormore other packet(s) in method 700.

Additionally or alternatively, in some instances, method 700 may resultin an improved quality of user experience for at least one user.

Alternatively to the example illustrated in FIG. 7, stages which areshown as being executed sequentially may in some other examples beexecuted in parallel, and/or stages shown as being executed in parallelmay in some other examples be executed sequentially. Alternatively toany of the example illustrated in FIG. 7, method 700 may in some otherexamples include more, fewer and/or different stages than illustrated.Alternatively to the example illustrated in FIG. 7, stages may in someother examples be executed in a different order than illustrated.

Although to ease the understanding of the reader, systems 470 and 670have been described separately, in some examples, there may be acombined system which may include some or all of the functionalityand/or one, some or all of the modules from system 470 and some or allof the functionality and/or one, some or all of the modules from system670. Such a combined system may be an example of supervisor system 170.Such a combined system may include any combination of software, hardwareand/or firmware. For example such a combined system or any part thereofmay include a computer. The subject matter does not limit thelocation(s) of system 470, 670 or a combination thereof, nor does thesubject matter limit whether or not module(s) of the system areconcentrated in one location or dispersed, but optionally at least partof the system may be located in a location between one or more PDN(s)190 and one or more base station(s) 130, and/or optionally at least partof the system may be in the same location as one or more base station(s)130 but at least logically separate from base station(s) 130.Additionally or alternatively, although to ease the understanding of thereader, methods 500 and 700 have been described separately, in someexamples there may be a combined method which may include one, some orall of the stages from method 500 and one, some or all of the stagesfrom method 700. Such a combined method may be an example of method 300.

Referring again to FIG. 1, for simplicity of illustration anddescription, there may be other element(s) which may be included inwireless network 100, depending on the architecture of wireless network100, which are not illustrated in nor described with reference toFIG. 1. For instance, there may be router(s), switch(es), and/or anyother element(s) which are not illustrated in FIG. 1. (Some examples ofsuch element(s) may be described and illustrated with reference to FIGS.8 and 9 below.) Depending on the example, any of the systems within thescope of the current subject matter (e.g. system 170, system 470, system670, a combination system, etc) or any part thereof may be a standaloneelement and/or may be integrated with any of these other element(s), ifexisting in network 100, such as with any router(s), switch(es), and/orany other suitable element(s). If any such system or any part thereof isintegrated with other element(s), the integrated system may, forinstance, include functionality of that system or part thereof and/orfunctionality of the other element(s). Additionally or alternatively forinstance, module(s) in the integrated system may include any module(s)within the scope of the current subject matter (e.g. shown in FIGS. 2,4, and/or 6, etc). Additionally or alternatively, for instance, theintegrated system may be configured to perform part or all of any methodwithin the scope of the current subject matter (e.g. method 300, 500,and/or 700, etc). Additionally or alternatively for instance, such anintegrated system may include any combination of software, hardwareand/or firmware. For example such an integrated system or any partthereof may include a computer. Additionally or alternatively, a systemnot integrated with such element(s), an integrated system, or any partthereof may or may not be integrated with base station 130, but in anyevent may be logically separate from base station 130. If base station130 is so integrated, a system which includes base station 130 and alsoincludes a system not integrated with such element(s), an integratedsystem, or any part thereof may for instance, include any combination ofsoftware, hardware and/or firmware. For example such a system (in whichbase station 130 is integrated) or any part thereof may include acomputer. Additionally or alternatively for instance, module(s) in sucha system may include any module(s) within the scope of the currentsubject matter (e.g. shown in FIGS. 2, 4, and/or 6, etc). Additionallyor alternatively for instance, such a system may be configured toperform part or all of any method within the scope of the currentsubject matter (e.g. method 300, 500, and/or 700, etc).

Although the subject matter does not impose limitations on thearchitecture of wireless network 100, for the sake of furtherillustration FIGS. 8 and 9 show some examples of architecture ofwireless network 100.

FIG. 8 is a block diagram of an example of a mobile network 800 with acore network of UNITS/GSM architecture, in accordance with the presentlydisclosed subject matter.

Network 800 may be an example of network 100 discussed above.

In the illustrated example, mobile network 800 may include one or morebase station controllers (BSCs) 822 and/or one or more radio networkcontrollers (RNCs) 820. For simplicity of illustration m (m≧1) BSC(s)822 and u (u≧1) RNC(s) 820 are illustrated in FIG. 8 and functionalityis described with reference to a first one of each. BSC 822 may be usedin GSM Enhanced Data rates for GSM Evolution (EDGE) architecture as wellas in combined UMTS/GSM architecture. RNC 528 may be used in UMTSarchitecture.

In the illustrated example, an interface 824 may interface between BSC522 and voice network 840 and/or a Gb interface 826 may interfacebetween BSC 822 and data network 860. An IuCS interface 830 mayinterface between RNC 828 and voice network 840 and/or an IuPS interface832 and/or an Iu-u interface 834 may interface between RNC 828 and datanetwork 860.

In the illustrated example, data network 860 and optionally voicenetwork 540 may be included in network 800. Although for simplicity ofillustration only one element of each type in networks 860 and 840 isillustrated in FIG. 8, it is possible that a different implementationmay include multiple elements of any given type.

Optionally mobile network 800 may include any of the following modules:Home Location Registrar (HLR) 850, Policy and charging rules function(PCRF) 852, Charging Gateway Function (CGF) 854, and/or Online ChargingSystem (OCS) 856.

Although for simplicity of illustration only one element of each ofthese types is illustrated in FIG. 8, it is possible that a differentimplementation may include multiple elements of any given type.

In the illustrated example, voice network 840 (when included), mayinclude a mobile switching center (MSC) 844. An interface 846 mayinterface between MSC 844 and MR 850. In the illustrated example, datanetwork 860 may include a Serving GPRS Node (SGSN), a Gateway GPRSSupport Node (GGSN), and optionally an Authentication, Authorization,and Accounting (AAA) server 875. A Gn/Gp interface 866 may interfacebetween SGSN 862 and GGSN 866. A Gr interface 864 may interface betweenSGSN 862 and HLR 850. A Gx interface 872 may interface between PCRF 852and GGSN 868. A Ga interface 874 may interface between CGF 854 and GGSN868. A Gy interface 876 may interface between OCS 856 and GGSN 868. ARemote Authentication Dial In User Service (RADIUS) protocol 875 may beused as a protocol between GGSN 868 and AAA server 878.

In the illustrated example, mobile network 800 may also include a PDN895 (an example of PDN 190). A Gi interface 870 may interface betweendata network 860 and PDN 895. Although for simplicity of illustrationonly one PDN 895 is illustrated in FIG. 8, it is possible that adifferent implementation may include multiple PDNs 895.

In the illustrated example, network 800 may optionally include one ormore switches to switch between controllers. For simplicity ofillustration, two switches 825 and 835 are shown which switch betweenBSCs 822 and between RNCs 828 respectively. Each BSC 822 may control oneor more base station(s) 815, also referred to as radio base station(s)or base transceiver station(s). For instance, fur simplicity ofillustration i (i>1) base station(s) 815 are shown and functionality isdescribed with reference to a first base station 815. Each RNC 828 maycontrol one or more base station(s) 817, also referred to as NodeB(s).For instance, for simplicity of illustration r (r≧1) base station(s) 817are shown and functionality is described with reference to a first basestation 817. Base station(s) 815 and/or base station(s) 817 may beexample(s) of base station 130. Each base station 815 may service one ormore group(s) served by one or more wireless transmitter(s) and therebyservice one or more UE(s) 110. For instance a first base station 815 isshown servicing j group(s) (j≧1) and therefore servicing k UE(s) 110(k≧1). For instance a first base station 817 is shown servicing sgroup(s) (s≧1) and therefore servicing t UE(s) 110 (t≧1).

Asterisks (“*”) in FIG. 8 illustrate possible locations of supervisor170 or at least a part thereof. Depending on the example, there may beone or more supervisor module(s) 170 in mobile network 800. Forinstance, a particular supervisor 170 or at least a part thereof may belocated between a particular base station 815 and respective BSC 822thereof, between a particular base station 817 and respective RNC 828thereof, in any BSC 822, in any RNC 828, between any RNC 828 andrespective switch thereof 835, between any BSC 822 and respective switchthereof 825, in any switch 825 and/or 835, between any switch 835 andSGSN 862, between any switch 825 and SGSN 862, between any switch 835and GGSN 868, between SSGN 862 and GGSN 868, between GGSN 568 and PUN595, in SGSN 862, and/or in GGSN 868, etc. Any particular supervisor 170or any part thereof may be configured to adopt one or more protocolsdepending on the location of supervisor module 170 or any part thereofin network 800.

FIG. 9 is a block diagram of an example of a mobile network including acore network of LTE architecture, in accordance with the presentlydisclosed subject matter.

Mobile network 900 may be an example of network 100 discussed above.

In the illustrated example, mobile network 900 may include a ServingGateway (SGW) 932, a Mobility Management Entity (MME) 926, a PUN Gateway(PGW) 938 and one or more base station(s) 915, also referred to aseNodeB(s). For instance, for simplicity of illustration x (x≧1) basestation(s) 915 are shown and functionality is described with referenceto a first base station 915. Base station 915 may be an example of basestation 130. An S1-U interface 924 may interface between base station915 and SGW 932. An S1-AP interface 922 may interface between basestation 915 and MME 926. An S11 interface 928 may interface between MME926 and SGW 932. An S5/S8 interface 934 may interface between SGW 932and PGW 938.

Optionally mobile network 900 may also include any of the following: aHome Subscriber Server (HSS) 936, a PCRF 940, an OCS 942, a CGF 944,and/or an AAA server 946. An S6a interface 930 may interface between MME926 and HSS 936. A Gy interface 948 may interface between OCS 942 andPGW 938. A Ga interface 950 may interface between CGF 944 and PGW 938. AGx interface 956 may interface between PCRF 940 and PGW 938. A RADIUSprotocol 952 may be used as a protocol between PGW 938 and AAA server946.

Although for simplicity of illustration only one element of type 926,927, 932, 936, 938, 950, 942, 944, and 946 in network 900 is illustratedin FIG. 9, it is possible that a different implementation may includemultiple elements of any given type.

In the illustrated example, mobile network 900 may also include a PDN995 (an example of PDN 190). An sGi interface 954 may interface betweenPGW 938 and PDN 995. Although for simplicity of illustration only onePDN 995 is illustrated in FIG. 9, it is possible that a differentimplementation may include multiple PDNs 995.

In the illustrated example, network 800 may optionally include one ormore switches to switch between base stations 915. For simplicity ofillustration, one switch 927 is shown. Network 900 may also includes oneor more user equipments(s) 110. Each base station 915 may service one ormore group(s) served by one or more wireless transmitter(s) and therebyservice one or more UE(s) 110. For instance a first base station 915 isshown servicing y group(s) (y≧1) and therefore servicing z UE(s) (z≧1).

Asterisks (“*”) in FIG. 9 illustrate possible locations of supervisor170 or at least a part thereof. Depending on the example, there may beone or more supervisor module(s) 170 in mobile network 900. Forinstance, a particular supervisor module 170 or at least a part thereofmay be located between base station 915 and switch 927, in switch 927,between switch 927 and MME 926, between switch 927 and SGW 932, betweenMME 926 and SGW 932, between SGW 932 and PGW 938, between PGW 938 andPDN 995, in MME 926, in SGW 932, and/or in PGW 938, etc. Any particularsupervisor 170 or any part thereof may be configured to adopt one ormore protocols depending on the location of supervisor 170 or any partthereof in network 900.

It will be understood that the subject matter contemplates, for example,a computer program being readable by a computer for executing a methodor part of a method disclosed herein. Further contemplated by thesubject matter, for example, is a computer-readable memory tangiblyembodying program code readable by a computer for executing a method orpart of a method disclosed herein.

EXAMPLES

-   1. A method of observing congestion in a wireless network,    comprising:

for a plurality of user equipments associated during a time span with aset comprising one or more groups served by one or more wirelesstransmitters, estimating parameters indicative of service to respectiveuser equipments;

comparing the estimated parameters or a function of the estimatedparameters to one or more thresholds;

determining whether or not said set is congested at least partly basedon a result of said comparing; and

if determined that said set is congested, outputting a report of saidcongestion.

-   2. The method of example 1, wherein said estimating and comparing    are performed a plurality of times during a time duration and    wherein said determining is based on at least one result from at    least one of said plurality of times that said comparing is    performed.-   3. The method of example 1, wherein an estimated one of said    parameters for a user equipment in said plurality, is a round trip    time.-   4. The method of example 1, wherein an estimated one of said    parameters for a user equipment in said plurality, is an adjusted    round trip time which is a difference between a round trip time and    a round trip time adjustment.-   5. The method of example 1, wherein said function is an average of    at least two estimated parameters respectively associated with at    least two user equipments in said plurality.-   6. The method of example 1, wherein said determining includes:    determining that said set is congested if a result of said comparing    is indicative of there being a predetermined percentage of the    plurality of user equipments whose round trip times or adjusted    round trip times are above one or more thresholds.-   7. The method of example 1, wherein said determining includes:    determining that said set is congested if a result of said comparing    is indicative of an average of round trip times or adjusted round    trip times being above a threshold.-   8. The method of example 1, wherein said determining includes: if    determined that said set is congested, determining a level of    congestion.-   9. The method of example 1, wherein said report includes an    indication of congestion.-   10. The method of example 1, wherein said report includes an    indication of level of congestion.-   11. The method of example 1, wherein said report is outputted to an    operator.-   12. The method of example 1, wherein said report is outputted to an    external element.-   13. The method of example 1, further comprising: outputting a report    regarding status of one or more queues in a base station servicing    said set.-   14. A system for observing congestion in a wireless network,    comprising:

a congestion evaluator configured, for a plurality of user equipmentsassociated during a time span with a set comprising one or more groupsserved by one or more wireless transmitters, to estimate parametersindicative of service to respective user equipments; said congestionevaluator further configured to compare the estimated parameters or afunction of the estimated parameters to one or more thresholds and todetermine whether or not said set is congested at least partly based ona result of said comparing; and

a reporter configured, if determined that said set is congested, tooutput a report of said congestion.

-   15. The system of example 14, further comprising: a noter configured    to note times associated with data packets, wherein estimation of a    parameter is at least partly based on one or more of said noted    times,-   16. The system of example 15, wherein said noter is further    configured to note sequence numbers associated with data packets,    wherein estimation of a parameter is at least partly based on one or    more of said noted sequence numbers.-   17. The system of example 14, further comprising: a recognizer    configured to recognize at least one selected from a group    comprising: user equipments for which respective data packets are    destined, one or more groups served by one or more wireless    transmitters associated with user equipments for which respective    data packets are destined, or a base station associated with user    equipments for which respective data packets are destined.-   18. The system of example 14, wherein at least part of said system    is located in the wireless network between a packet data network and    one or more base stations.-   19. A computer program product comprising a computer useable medium    having computer readable code embodied therein for observing    congestion in a wireless network, the computer program product    comprising:

computer readable program code for causing a computer to, for aplurality of user equipments associated during a time span with a setcomprising one or more groups served by one or more wirelesstransmitters, estimate parameters indicative of service to respectiveuser equipments;

computer readable program code for causing a computer to compare theestimated parameters or a function of the estimated parameters to one ormore thresholds;

computer readable program code for causing a computer determine whetheror not said set is congested at least partly based on a result of saidcomparing; and

computer readable program code for causing a computer, if it isdetermined that said set is congested, to output a report of saidcongestion.

-   20. The computer program product of example 19, further comprising:

computer readable code for causing the computer to note times associatedwith data packets, wherein estimation of a parameter is at least partlybased on one or more of said noted times.

-   21. A method of affecting data in a wireless network, comprising:

estimating a parameter indicative of service by a base station to anyone of a plurality of user equipments or to said plurality of userequipments;

at least partly based on said estimated parameter, determining whetheror not to adjust delaying of arrival at the base station of at least onedata packet; and

if determined to adjust delaying, adjusting delaying of arrival of saidat least one data packet.

-   22. The method of example 21, wherein said parameter is indicative    of a base station outgoing rate.-   23. The method of example 22, wherein said parameter is a base    station outgoing rate to said plurality of user equipments, said    estimating including:

determining an average of respective round trip times or functionsthereof for the plurality of user equipments;

if necessary, causing an incoming rate into the base station for theplurality of user equipments to change until the average is steady; and

estimating that said outgoing rate to said plurality of user equipmentsis approximately equal to the incoming rate into the base station forthe plurality of user equipments, when said average is steady;

and wherein said determining whether or not to adjust delaying includes:

comparing said estimated outgoing rate to a minimum required rate fordata to the plurality of user equipments; and

determining to delay arrival at the base station of at least one datapacket destined for any of the plurality of user equipments if a resultof said comparing is indicative that said estimated outgoing rate isless than said minimum required rate.

-   24. The method of example 22, wherein said parameter is a base    station outgoing rate to a certain user equipment in said plurality    of user equipments, and wherein said plurality of user equipments    compete for service by said base station, said estimating including:

estimating said outgoing rate while the base station is not providingdata packets to any other of the plurality of user equipments, saidoutgoing rate being indicative of reception conditions for the certainuser equipment; and

wherein said determining whether or not to adjust delaying includes:

comparing said estimated outgoing rate to a minimum required rate fordata to the certain user equipment; and

determining to delay arrival at the base station of at least one datapacket destined for the certain user equipment if a result of saidcomparing is indicative that said estimated outgoing rate is less thansaid minimum required rate.

-   25. The method of example 21, wherein said parameter is estimated    after an interval, and said parameter is indicative of base station    queuing time, and wherein said determining includes:

comparing said estimated parameter to a length of said interval, orcomparing parameters estimated for respective user equipments in saidplurality to said length; and

determining to not delay or to stop delaying arrival at the base stationof at least one data packet if a result of said comparing is indicativethat base station queuing time is too short.

-   26. The method of example 21, wherein said parameter is indicative    of base station queuing time and wherein said determining includes:

comparing said estimated parameter to a maximum desired base stationqueuing time or comparing parameters estimated for respective userequipments in said plurality to said maximum desired base stationqueuing time; and

determining to delay arrival at the base station of at least one datapacket if a result of said comparing is indicative that base stationqueuing time is too long.

-   27. The method of example 21, wherein said parameter is a round trip    time, an adjusted round trip time, an average round trip time, or an    average adjusted round trip time.-   28. The method of example 21, wherein said determining includes:    determining to adjust delaying arrival at the base station of at    least one data packet if said parameter is not steady.-   29. The method of example 21, wherein said parameter is indicative    of data packets being provided by the base station to more than one    of said plurality of user equipments which compete for service, and    wherein said determining includes: determining to delay arrival at    the base station of data packets destined for any but one of said    plurality of user equipments.-   30. The method of example 21, wherein said determining includes:    determining whether or not to adjust delaying of a certain data    packet at least partly based on data packet type.-   31. The method of example 30, wherein whether or not to adjust    delaying is at least partly based on whether or not said data packet    type is a data packet type for which a high quality of user    experience is at least partly dependent on a constant rate to an    associated user equipment.-   32. The method of example 21, wherein said determining includes:    determining whether or not to adjust delaying of a certain data    packet at least partly based on to which user equipment said data    packet is destined.-   33. The method of example 21, wherein estimating is performed a    plurality of times and wherein said determining is at least partly    based on at least one parameter estimated during at least one of    said plurality of times.-   34. A system for affecting data in a wireless network, comprising:

a delay evaluator configured to estimate a parameter indicative ofservice by a base station to any one of a plurality of user equipmentsor to said plurality of user equipments; and to at least partly based onsaid estimated parameter, determine whether or not to adjust delaying ofarrival at the base station of at least one data packet; and

a delayer configured, if determined to adjust delaying, to adjustdelaying of arrival of said at least one data packet.

-   35. The system of example 34, further comprising: a noter configured    to note times associated with data packets, wherein estimation of a    parameter is at least partly based on one or more of said noted    times.-   36. The system of example 35, wherein said noter is further    configured to note sequence numbers associated with data packets,    wherein estimation of a parameter is at least partly based on one or    more of said noted sequence numbers.-   37. The system of example 34, further comprising: a recognizer    configured to recognize at least one selected from a group    comprising: user equipments for which respective data packets are    destined, one or more groups served by one or more wireless    transmitters associated with user equipments for which respective    data packets are destined, or types of respective data packets.-   38. The system of example 34, further comprising at least one data    packet queue.-   39. The system of example 34, wherein at least part of said system    is located in the wireless network between a packet data network and    one or more base stations.-   40. A computer program product comprising a computer useable medium    having computer readable code embodied therein for affecting data in    a wireless network the computer program product comprising:

computer readable program code for causing a computer to estimate aparameter indicative of service by a base station to any one of aplurality of user equipments or to said plurality of user equipments;

computer readable program code for causing a computer to, at leastpartly based on said estimated parameter, determine whether or not toadjust delaying arrival at the base station of at least one data packet;and

computer readable program code for causing a computer to, if determinedto adjust delaying, to adjusting delaying of arrival of said at leastone data packet.

-   41. The method of example 21, wherein said determining is at least    partly based on quality of experience considerations.-   42. The system of example 34, wherein said determining is at least    partly based on quality of experience considerations.-   43. The computer program product of example 40, wherein said    determining is at least partly based on quality of experience    considerations.-   44. A method of supervising data in a wireless network, comprising:

noting times associated with data packets en route between a packet datanetwork and a base station;

at least partly based on one or more of said noted times, evaluating theservice provided by the base station;

at least partly based on a result of said evaluating, determiningwhether or not at least one action should be performed; and

if determined that any action should be performed, performing at leastone action.

-   45. The method of example 44, wherein said evaluating includes:    estimating at least one parameter at least partly based on one or    more of said noted times.-   46. The method of example 45, wherein at least one of said at least    one parameter is indicative of base station queuing time.-   47. The method of example 45, wherein at least one of said at least    one parameter is a round trip time or adjusted round trip time.-   48. The method of example 45, wherein at least one of said at least    one parameter is a base station outgoing rate.-   49. A system for supervising data in a wireless network, comprising:

a noter configured to note times associated with data packets en routebetween a packet data network and a base station;

an evaluator configured, at least partly based on one or more of saidnoted times, to evaluate the service provided by the base station, andconfigured, at least partly based on a result of said evaluating, todetermine whether or not at least one action should be performed; and

an action performer delayer configured, if determined that any actionshould be performed, to perform at least one action.

-   50. The system of example 49, further comprising: a data structure    in which said noter is configured to store times associated with    data packets.-   51. The system of example 49, further comprising: a recognizer    configured to recognize characteristics of data packets.-   52. The system of example 49, further comprising: a handler    configured to intercept and forward data packets.-   53. The system of example 49, wherein at least part of said system    is located in the wireless network between a packet data network and    one or more base stations.-   54. A computer program product comprising a computer useable medium    having computer readable code embodied therein for supervising data    in a wireless network, the computer program product comprising:

computer readable program code for causing a computer to note timesassociated with data packets en route between a packet data network andabuse station;

computer readable program code for causing a computer, at least partlybased on one or more of said noted times, to evaluate the serviceprovided by the base station;

computer readable program code for causing a computer, at least partlybased on a result of said evaluating, to determine whether or not atleast one action should be performed; and

computer readable program code for causing a computer, if determinedthat any action should be performed, to perform at least one action.

-   55. The method of example 44, wherein at least one of said at least    one action is performed in order to reduce the fullness of at least    one queue in the base station.-   56. The system of example 49, wherein at least one of said at least    one action is performed in order to reduce the fullness of at least    one queue in the base station.-   57. The computer program product of example 54, wherein at least one    of said at least one action is performed in order to reduce the    fullness of at least one queue in the base station.-   58. A method of reducing a time period for a packet to travel to a    respective user equipment in a wireless network comprising:

estimating a parameter indicative of service by a base station;

at least partly based on said estimated parameter, determining whetheror not to delay arrival at the base station of at least one other datapacket so as to reduce the time period for the packet to travel to therespective user equipment; and

if determined to delay, delaying of arrival of the at least one otherdata packet.

-   59. The method of example 58, wherein said parameter is indicative    of base station queuing time and wherein said determining includes:

comparing one or more estimated parameters to a maximum desired queuingtime; and

determining to delay arrival at the base station of the at least oneother data packet result of said comparing is indicative that basestation queuing time is too long.

-   60. The method of example 58, wherein said parameter is a round trip    time, an adjusted round trip time, an average round trip time, or an    average adjusted round trip time.-   61. The method of example 58, wherein said determining includes:    determining whether or not to delay arrival of a certain data packet    at least partly based on data packet type.-   62. The method of example 61, wherein whether or not to delay is at    least partly based on whether or not said data packet type is a data    packet type for which a high quality of user experience is at least    partly dependent on a constant rate to an associated user equipment.-   63. The method of example 58, wherein said determining includes:    determining whether or not to delay arrival of a certain data packet    at least partly based on to which user equipment said data packet is    destined.-   64. The method of example 58, wherein estimating is performed a    plurality of times and wherein said determining is at least partly    based on at least one parameter estimated during at least one of    said plurality of times.-   65. The method of example 58, wherein said estimated parameter    relates to one user equipment or to a plurality of user equipments.-   66. The method of example 58, further comprising: noting times    associated with data packets, wherein said estimating of a parameter    is at least partly based on one or more of said noted times.-   67. A system for reducing a time period for a packet to travel to a    respective user equipment in a wireless network, comprising:

a delay evaluator configured to estimate a parameter indicative ofservice by a base station; and to at least partly based on saidestimated parameter, determine whether or not to delay arrival at thebase station of at least one other data packet so as to reduce the timeperiod for the packet to travel to the respective user equipment; and

a delayer configured, if determined to delay, to delay arrival of the atleast one other data packet.

-   68. The system of example 67, further comprising: a noter configured    to note times associated with data packets, wherein estimation of a    parameter is at least partly based on one or more of said noted    times.-   69. The system of example 68, wherein said noter is further    configured to note sequence numbers associated with data packets,    wherein estimation of a parameter is at least partly based on one or    more of said noted sequence numbers.-   70. The system of example 67, further comprising: a recognizer    configured to recognize at least one selected from a group    comprising: user equipments for which respective data packets are    destined, one or more groups served by one or more wireless    transmitters associated with user equipments for which respective    data packets are destined, or types of respective data packets.-   71. The system of example 67, further comprising at east one data    packet queue.-   72. The system of example 67, wherein at least part of said system    is located in the wireless network between a packet data network and    one or more base stations.-   73. A computer program product comprising a computer useable medium    having computer readable code embodied therein for reducing a time    period for a packet to travel to a respective user equipment in a    wireless network, the computer program product comprising:

computer readable program code for causing a computer to estimate aparameter indicative of service by a base station;

computer readable program code for causing a computer to, at leastpartly based on said estimated parameter, determine whether or not todelay arrival at the base station of at least one other data packet soas to reduce the time period for the packet to travel to the respectiveuser equipment; and

computer readable program code for causing a computer to, if determinedto delay, to delay arrival of said at least one other data packet.

-   74. The computer program product of example 73, wherein said    parameter is indicative of base station queuing time and wherein    said computer readable program code for causing a computer to    determine includes:

computer readable program code for causing a computer to compare one ormore estimated parameters to a maximum desired queuing time; and

computer readable program code for causing a computer to determine todelay arrival at the base station of the at least one other data packetif a result of said comparing is indicative that base station queuingtime is too long.

-   75. The computer program product of example 73, wherein said    parameter is a round trip time, an adjusted round trip time, an    average round trip time, or an average adjusted round trip time.-   76. The computer program product of example 73, further comprising:    computer readable program code for causing a computer to note times    associated with data packets, wherein estimation of a parameter is    at least partly based on one or more of said noted times.-   77. The computer program product of example 73, wherein said    estimated parameter relates to one user equipment or to a plurality    of user equipments.

While examples of the subject matter have been shown and described, thesubject matter is not thus limited. Numerous modifications, changes andimprovements within the scope of the subject matter will now occur tothe reader.

1. A method of supervising data in a wireless network, comprising:noting times associated with data packets en route between a packet datanetwork and a base station; at least partly based on one or more of saidnoted times, evaluating the service provided by the base station; atleast partly based on a result of said evaluating, determining whetheror not at least one action should be performed; and if determined thatany action should be performed, performing at least one action.
 2. Themethod of claim 1, wherein said evaluating includes: estimating at leastone parameter at least partly based on one or more of said noted times,3. The method of claim 2, wherein at least one of said at least oneparameter is indicative of base station queuing time.
 4. The method ofclaim 2, wherein at least one of said at least one parameter is a roundtrip time or adjusted round trip time.
 5. The method of claim 2, whereinat least one of said at least one parameter is a base station outgoingrate.
 6. A system for supervising data in a wireless network,comprising: a noter configured to note times associated with datapackets en route between a packet data network and a base station; anevaluator configured, at least partly based on one or more of said notedtimes, to evaluate the service provided by the base station, andconfigured, at least partly based on a result of said evaluating, todetermine whether or not at least one action should be performed; and anaction performer delayer configured, if determined that any actionshould be performed, to perform at least one action.
 7. The system ofclaim 6, further comprising: a data structure in which said noter isconfigured to store times associated with data packets.
 8. The system ofclaim 6, further comprising: a recognizer configured to recognizecharacteristics of data packets.
 9. The system of claim 6, furthercomprising: a handler configured to intercept and forward data packets,10. The system of claim 6, wherein at least part of said system islocated in the wireless network between a packet data network and one ormore base stations.
 11. A computer program product comprising a computeruseable medium having computer readable code embodied therein forsupervising data in a wireless network, the computer program productcomprising: computer readable program code for causing a computer tonote times associated with data packets en route between a packet datanetwork and a base station; computer readable program code for causing acomputer, at least partly based on one or more of said noted times, toevaluate the service provided by the base station; computer readableprogram code for causing a computer, at least partly based on a resultof said evaluating, to determine whether or not at least one actionshould be performed; and computer readable program code for causing acomputer, if determined that any action should be performed, to performat least one action.
 12. The method of claim 1, wherein at least one ofsaid at least one action is performed in order to reduce the fullness ofat least one queue in the base station.
 13. The system of claim 6,wherein at least one of said at least one action is performed in orderto reduce the fullness of at least one queue in the base station. 14.The computer program product of claim 11, wherein at least one of saidat least one action is performed in order to reduce the fullness of atleast one queue in the base station.